A Query Pipeline transforms a set of inputs into a Solr query request and it can execute requests and manipulate the Solr response as well, via a set of modularized operations called Query Stages. The objects sent from stage to stage are Request objects and Response objects.
Fusion stores pipeline names and definitions, allowing a pipeline to be reused across applications. Pipeline definitions can be modified, so that as an application evolves, the pipelines used by that application can evolve accordingly. During application development, the Fusion UI can be used to develop and debug a Query Pipeline.
The available stage types allow setting specific parameters for the query, such as the number of results to return or the query parser to use. You can also define facets and recommendations to be returned with the results. If Access Control Lists (ACLs) are in use, you can apply a security-trimming stage to apply user access restrictions to the results.
Default Query Pipelines
When you create a new app with a default collection, the collection includes a default query pipeline. When you create a new collection in an existing app, Fusion also creates a default query pipeline for the new collection. The pipeline name is the same as the collection name.
The default query pipeline has the following pre-configured stages:
This stage queries the
_signals_aggr collection (typically generated by the
_click_signals_aggregation Spark job), using the query parameters configured in the stage, and returns document recommendations with boost weights.
Unresolved directive in query-pipelines.asciidoc - include::/fusion-server/reference-guides/query-pipeline-stages/query-pipeline-stages/search-fields-query-stage.asciidoc[tag=intro]
The Field Facet query pipeline stage is used to add a Solr Field Facet query to the search query pipeline.
The Solr Query stage transforms the Fusion query pipeline Request object into a Solr query and sends it to Solr.