Uses of Class
com.yahoo.schema.processing.Processor
Package
Description
Classes in this package (processors) implements some search
definition features by reducing them to simpler features.
-
Uses of Processor in com.yahoo.schema
Modifier and TypeMethodDescriptionApplicationBuilder.processorsToSkip()
Returns a modifiable set of processors we should skip for these schemas.ModifierConstructorDescriptionApplication
(com.yahoo.config.application.api.ApplicationPackage applicationPackage, List<Schema> schemas, RankProfileRegistry rankProfileRegistry, QueryProfiles queryProfiles, com.yahoo.config.model.api.ModelContext.Properties properties, boolean documentsOnly, boolean validate, Set<Class<? extends Processor>> processorsToSkip, com.yahoo.config.application.api.DeployLogger logger) -
Uses of Processor in com.yahoo.schema.processing
Modifier and TypeClassDescriptionclass
Adds the attribute summary transform (SummaryTransform.ATTRIBUTE
to allSummaryField
having an imported field as source.class
This processor creates aSDDocumentType
for eachSchema
object which holds all the data that search associates with a document described in a search definition file.class
class
Checks that attribute properties only are set for attributes that have data (are created by an indexing statement).class
Fields that derive to attribute(s) and no indices should use the WORD indexing form, in a feeble attempt to match the most peoples expectations as closely as possible.class
Checks that bolding or dynamic summary is turned on only for text fields.class
Validates attribute fields using bool type, ensuring the collection type is supported.class
Adds field sets for 1) fields defined inside document type 2) fields inside search but outside documentclass
Adds a "fieldName_zcurve" long attribute and "fieldName.distance" and "FieldName.position" summary fields to all position type fields.class
Propagates dictionary settings from field level to attribute level.class
Non-primitive key types for map and weighted set forbidden (though OK in document model)class
class
The implementation of exact matchingclass
Validates the use of the fast-access property.class
Computes the right "index commands" for each fieldset in a search definition.class
Takes the fields and indexes that are of type rank filter, and stores those names on all rank profilesclass
Makes implicitly defined summaries into explicit summariesclass
This processor adds all implicit summary fields to all registered document summaries.class
Iterates all imported fields from schema parsing and validates and resolves them into concrete fields from referenced document types.class
Because of the way the parser works (allowing any token as identifier), it is not practical to limit the syntax of field names there, do it here.class
This processor modifies all indexing scripts so that they input the value of the owning field by default.class
This processor modifies all indexing scripts so that they output to the owning field by default.class
class
class
Replaces the 'index' statement of all numerical fields to 'attribute' because we no longer support numerical indexes.class
Expresses literal boosts in terms of extra indices with rank boost.class
Takes the aliases set on field by parser and sets them on correct Index or Attributeclass
All summary fields which are not attributes must currently be present in the default summary class, since the default summary class also defines the docsum.dat format.class
Warn on inconsistent match settings for any indexclass
Iterates all summary fields with 'matched-elements-only' and adjusts transform (if all struct-fields are attributes) and validates that the field type is supported.class
Validates the match phase settings for all registered rank profiles.class
Ensures that there are no conflicting types or field settings in multifield indices, either by changing settings or by splitting conflicting fields in multiple ones with different settings.class
class
The implementation of "gram" matching - splitting the incoming text and the queries into n-grams for matching.class
Processes ONNX ranking features of the form: onnx("files/model.onnx", "path/to/output:1") And generates an "onnx-model" configuration as if it was defined in the profile: onnx-model files_model_onnx { file: "files/model.onnx" } Inputs and outputs are resolved in OnnxModelTypeResolver, which must be processed after this.class
Processes every "onnx-model" element in the schema.class
Run ExpressionOptimizer on all scripts, to get rid of expressions that have no effect.class
Validates the 'paged' attribute setting and throws if specified on unsupported types.class
Validates the predicate fields.class
Resolves and assigns types to all functions in a ranking expression, and validates the types of all ranking expressions under a schema instance: Some operators constrain the types of inputs, and first-and second-phase expressions must return scalar values.class
Class that processes reference fields and removes attribute aspect of such fields from summary.class
class
Issues a warning if some function has a reserved name.class
A search must have a document definition of the same name inside of it, otherwise crashes may occur as late as during feedingclass
All rank: filter fields should have rank type empty.class
Validate conflicting settings for sortingclass
class
Ensure that summary field transforms for fields having the same name are consistent across summary classesclass
Emits a warning for summaries which accesses disk.class
Fail if: An SD field explicitly says summary:dynamic , but the field is non-string array, wset, or struct.class
Verifies that the source fields actually refers to a valid field.class
Verifies that equally named summary fields in different summary classes don't use different fields for source.class
Adds the corresponding summary transform for all "documentid" summary fields.class
The implementation of the tag datatypeclass
Class that processes and validates tensor fields.class
class
class
class
This Processor makes sure all fields with the same name have the sameDataType
.class
class
Check that fields with index settings actually creates an index or attributeclass
class
The implementation of word matching - with word matching the field is assumed to contain a single "word" - some contiguous sequence of word and number characters - but without changing the data at the indexing side (as with text matching) to enforce this.Modifier and TypeMethodDescriptionProcessing.ProcessorFactory.create
(Schema schema, com.yahoo.config.application.api.DeployLogger deployLogger, RankProfileRegistry rankProfileRegistry, QueryProfiles queryProfiles) Modifier and TypeMethodDescriptionvoid
Processing.process
(Schema schema, com.yahoo.config.application.api.DeployLogger deployLogger, RankProfileRegistry rankProfileRegistry, QueryProfiles queryProfiles, boolean validate, boolean documentsOnly, Set<Class<? extends Processor>> processorsToSkip) Runs all search processors on the givenSchema
object. -
Uses of Processor in com.yahoo.schema.processing.multifieldresolver
Modifier and TypeClassDescriptionclass
This processes a schema and adds input type settings on all rank profiles.