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 Fusion UI for more information.
For 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 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. 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 Fusion license, it is only effective after running Fusion jobs or creating Fusion rules. See Query Rewriting for details.

Query pipeline stage condition examples

Stages can be triggered conditionally when a script in the Condition field evaluates to true. Some examples are shown below. Run this stage only for mobile clients:
params.deviceType === "mobile"
Run this stage when debugging is enabled:
params.debug === "true"
Run this stage when the query includes a specific term:
params.q && params.q.includes("sale")
Run this stage when multiple conditions are met:
request.hasParam("fusion-user-name") && request.getFirstParam("fusion-user-name").equals("SuperUser");
!request.hasParam("isFusionPluginQuery")
The first condition checks that the request parameter “fusion-user-name” is present and has the value “SuperUser”. The second condition checks that the request parameter “isFusionPluginQuery” is not present.

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.