XML Configuration Reference : Search : CompoundWordSplitter
 
CompoundWordSplitter
com.exalead.indexing.analysis.v10.CompoundWordSplitter
Annotates compound words that use CamelCase (like SearchServer) or underscores (like my_variable) to separate the root words. This allows users to search for the root words individually. Annotations generated:
"compound": for example, compound="search server"
Parent elements:
com.exalead.mercury.mami.search.v20.SemanticProcessorModule (as SemanticProcessorModule)
com.exalead.mercury.mami.search.v20.SemanticQueryAnalysisConfig (as SemanticQueryAnalysisConfig)
Attributes:
Name
Type
Default value
Description
name
string
Name of the Semantic Processor. This name is only used for tracing and debugging purposes.
contexts
string
Comma-separated list of the ContextNames of the Document Chunks on which this processor should be applied. If this list is empty, all DocumentChunks are processed.
dataModelState
string
Is this semantic processor managed by a data model? @enum{null,auto,customized, error}. If null, this semantic processor is not related to the data model. If "auto", this semantic processor is auto-generated by the data model.
dataModelClass
string
If dataModelState is either "auto" or "customized", you will find here the name of the DataModelClass that generated this DocumentProcessor.
dataModelProperty
string
If dataModelState is either "auto" or "customized", you will find here the name of the DataModelProperty that generated this DocumentProcessor.
disabled
boolean
Disables the DocumentProcessor
tokenizeAnnotations
boolean
True
Subtokenizes "SearchServer" into "Search" "Server" automatically, and keep original annotations.
doCamelCase
boolean
True
Separates compound words before each capital letter. For example, the annotation for "CamelCase" is compound="camel case".
doUnderscore
boolean
True
Separates multi-word strings wherever there is an underscore. For example, the annotation for "under_score" is compound="under score".
Nested elements:
Name
Type
Description
fromDataModel
com.exalead.indexing.analysis.v10.SemanticProcessor
If dataModelState is "customized", you will find here the original semantic processor generated by the data model. Use this to easily revert to "auto" state from "customized". @IgnoreForValueConstructor