Text Tagger Stage

This stage uses the SolrTextTagger handler to identify known entities in the query by searching the _query_rewrite collection (or the _query_rewrite_staging collection in the case of the Fusion AI query rewriting Simulator) to find matching spelling corrections, phrase boosts, underperforming query improvements, and synonym expansions in order to perform query rewriting.

By default, rewrite lookup is done based on text value of the main query. For Legacy requests this is the value of the 'q' parameter. For requests made using Fusion’s query DSL the value of the userQuery property is used instead.

When the query rewrite entails boosting, the boosting is applied later in the pipeline, during the Solr Query stage.

The underlying SolrTextTagger currently only supports single-shard collections. Fusion users should ensure their _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 Fusion AI license, it is only effective after running Fusion AI jobs or creating Fusion AI rules. See Query Rewriting for details.


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.