Uses of Class
com.yahoo.schema.processing.Processor
Packages that use 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
Methods in com.yahoo.schema that return types with arguments of type ProcessorModifier and TypeMethodDescriptionApplicationBuilder.processorsToSkip()Returns a modifiable set of processors we should skip for these schemas.Constructor parameters in com.yahoo.schema with type arguments of type ProcessorModifierConstructorDescriptionApplication(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
Subclasses of Processor in com.yahoo.schema.processingModifier and TypeClassDescriptionclassAdds the data type and attribute summary transform (SummaryTransform.ATTRIBUTEto allSummaryFieldhaving an imported field as source.classThis processor creates aSDDocumentTypefor eachSchemaobject which holds all the data that search associates with a document described in a search definition file.classclassAdds the corresponding summary transform for all "documentid" summary fields.classChecks that attribute properties only are set for attributes that have data (are created by an indexing statement).classFields 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.classChecks that bolding or dynamic summary is turned on only for text fields.classAdds field sets for 1) fields defined inside document type 2) fields inside search but outside documentclassAdds a "fieldName_zcurve" long attribute and "fieldName.distance" and "FieldName.position" summary fields to all position type fields.classPropagates dictionary settings from field level to attribute level.classNon-primitive key types for map and weighted set forbidden (though OK in document model)classclassThe implementation of exact matchingclassValidates the use of the fast-access property.classComputes the right "index commands" for each fieldset in a search definition.classTakes the fields and indexes that are of type rank filter, and stores those names on all rank profilesclassMakes implicitly defined summaries into explicit summariesclassThis processor adds all implicit summary fields to all registered document summaries.classIterates all imported fields from schema parsing and validates and resolves them into concrete fields from referenced document types.classBecause 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.classThis processor modifies all indexing scripts so that they input the value of the owning field by default.classThis processor modifies all indexing scripts so that they output to the owning field by default.classclassclassReplaces the 'index' statement of all numerical fields to 'attribute' because we no longer support numerical indexes.classExpresses literal boosts in terms of extra indices with rank boost.classTakes the aliases set on field by parser and sets them on correct Index or AttributeclassAll 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.classWarn on inconsistent match settings for any indexclassValidates the match phase settings for all registered rank profiles.classEnsures 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.classclassThe implementation of "gram" matching - splitting the incoming text and the queries into n-grams for matching.classProcesses 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.classProcesses every "onnx-model" element in the schema.classRun ExpressionOptimizer on all scripts, to get rid of expressions that have no effect.classValidates the 'paged' attribute setting and throws if specified on unsupported types.classValidates the predicate fields.classResolves 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.classClass that processes reference fields and removes attribute aspect of such fields from summary.classclassIssues a warning if some function has a reserved name.classA search must have a document definition of the same name inside of it, otherwise crashes may occur as late as during feedingclassAll rank: filter fields should have rank type empty.classValidates attribute fields using bool type, ensuring the collection type is supported.classValidate conflicting settings for sortingclassclassEnsure that summary field transforms for fields having the same name are consistent across summary classesclassEmits a warning for summaries which accesses disk.classFail if: An SD field explicitly says summary:dynamic , but the field is non-string array, wset, or struct.classIterates all summary fields with 'matched-elements-only' or 'select-elements-by' and validates that the field type is supported.classVerifies that the source fields actually refers to a valid field.classVerifies that equally named summary fields in different summary classes don't use different fields for source.classThe implementation of the tag datatypeclassClass that processes and validates tensor fields.classclassclassclassclassThis Processor makes sure all fields with the same name have the sameDataType.classclassCheck that fields with index settings actually creates an index or attributeclassProcessor which validates that a fieldfoocannot be declared as bothclassclassThe 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.Methods in com.yahoo.schema.processing that return ProcessorModifier and TypeMethodDescriptionProcessing.ProcessorFactory.create(Schema schema, com.yahoo.config.application.api.DeployLogger deployLogger, RankProfileRegistry rankProfileRegistry, QueryProfiles queryProfiles) Method parameters in com.yahoo.schema.processing with type arguments of type ProcessorModifier and TypeMethodDescriptionvoidProcessing.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 givenSchemaobject. -
Uses of Processor in com.yahoo.schema.processing.multifieldresolver
Subclasses of Processor in com.yahoo.schema.processing.multifieldresolverModifier and TypeClassDescriptionclassThis processes a schema and adds input type settings on all rank profiles.