Query Pipeline Management
- What Is a Query Pipeline
- Routing Mechanisms and Rules
- Deployment Overview
- Order of Execution of Query Pipeline Features
- Troubleshooting Query Pipeline Rules
- Coveo ML Model Association Management
- Associate a Model via a JSON Configuration
- Thesaurus Rule Management
- Featured Results Rule Management
- Stop Words Rule Management
- Ranking Expressions Rule Management
- Ranking Weights Rule Management
- Triggers Rule Management
- Filters Rule Management
- Query Parameters Rule Management
- Query Pipeline Rule Management
- Coding Query Pipeline Rules
- Testing Changes
- Exporting and Importing Query Pipeline Elements
What Is a Query Pipeline?
In your Coveo Cloud organization, a query pipeline is an alternate set of rules or models that can be defined to modify queries. You can define query pipelines from the Coveo Cloud administration console (see Adding and Managing Query Pipelines).
You can take advantage of query pipelines when you have more than one search interface with distinct users and purpose and want to apply different rules or models for each.
Your customers and partners use your community portal to self-serve and find relevant information, while your support agents access an internal service portal to find relevant public and private items. You can create a separate pipeline for each portal, defining appropriate rules for each search interface audience.
You can also use query pipeline A/B testing to evaluate rule or model changes on a part of the users (see Adding and Managing A/B Tests).
Query pipeline rules can define:
Thesaurus entries - replacing or expanding queries with synonyms (see Adding and Managing Query Pipeline Thesaurus Rules)
Featured results - items appearing at the top of search results when the query meets a specific condition (see Adding and Managing Query Pipeline Featured Results)
Filters - adding hidden query expressions to all queries that go through the query pipeline (see Adding and Managing Query Pipeline Filters)
Query parameters - overriding search parameter values for every query that goes through the query pipeline (see Adding and Managing Query Pipeline Query Parameters)
Ranking rules - modifying the order of results matching specified expressions and conditions (see Adding and Managing Query Pipeline Ranking Expressions)
Ranking weights - establishing the impact of ranking factors when establishing the order of results (see Adding and Managing Query Pipeline Ranking Weight Rules)
Stop words - ignoring unimportant words in queries (see Adding and Managing Query Pipeline Stop Words)
Triggers - establishing actions to be performed in the user search interface following an event when a condition is met (see Adding and Managing Query Pipeline Triggers)
Some rules can be applied on the query before it is sent to the index (like thesaurus and stop words), while others are applied on the results returned by the index before they are sent back to the search interface (like featured results and ranking rules).
Query pipeline associated models can define:
Automatic Relevance Tuning (ART) - optimizing search results relevance based on user search behavior
Query Suggestions - suggesting queries to users as they type in a search box
Event Recommendations - predicting and proposing the most relevant content for the current user in the current session
Understand how to create and use a query pipeline (see Query Pipeline Deployment Overview).