This stage uses the SolrTextTagger handler to identify known entities in the query by searching the COLLECTION_NAME_query_rewrite collection. See Manage Collections in the Managed Fusion UI for more information.
For Managed Fusion 5.x.x organizations that do not have a Predictive Merchandiser license, the Solr Text Tagger handler also searches the COLLECTION_NAME_query_rewrite_staging collection in the case of the Managed Fusion query rewriting Simulator).
The purpose of the search is to perform query rewriting using matches from the following items: When the query rewrite entails boosting, the boosting is applied later in the pipeline, during the Solr Query stage. The below diagram shows the process flow for the Text Tagger Stage: Text Tagger Stage Process
The underlying SolrTextTagger currently only supports single-shard collections. Managed Fusion users should ensure their COLLECTION_NAME_query_rewrite collection, or whatever collection the Text Tagger stage is configured to use, is single-sharded before enabling this stage.
Although this stage is available without a Managed Fusion license, it is only effective after running Managed Fusion jobs or creating Managed Fusion rules. See Query Rewriting for details.

Configuration

When entering configuration values in the UI, use unescaped characters, such as \t for the tab character. When entering configuration values in the API, use escaped characters, such as \\t for the tab character.