Stop - Query Pipeline Feature
Typically, a statement expressing the
stop feature should only apply when a certain condition is fulfilled.
In general, you should ensure that this is the case by associating such a statement, and/or the query pipeline it is defined in, to a global condition.
- In the Coveo Cloud administration console, you can manage statements expressing the
stopfeature from the Stop Words tab (see Adding and Managing Query Pipeline Stop Words).
- The Intelligent Term Detection (ITD) Coveo Machine Learning (Coveo ML) feature takes statements expressing the
stopfeature into account before injecting keywords from the large query expression (
lq) into the basic query expression.
The following diagram shows the process of a query being sent to the Search API and the order of execution of query pipeline features.
Use the following QPL syntax to define a statement expressing the
<words>is a comma-separated list of quoted strings where each element defines a case-insensitive word that should be removed from the basic query expression (e.g.,
"foo", "bar", "baz").
A given stop word instance will not be removed from the basic query expression when:
- The condition associated to the statement is not fulfilled.
- The stop word instance appears in an exact phrase match term in the current basic query expression.
- The current basic query expression only contains stop words.
- The stop word instance is acting as an operand of a boolean query syntax operator in the current basic query expression.
In an empty query pipeline named
Testing Stop, you define a statement expressing the
stop feature with the following QPL definition:
stop "be", "do", "how", "i", "in", "my", "not", "or", "the", "to"
The following table shows how the basic query expression of different queries going through the
Testing Stop query pipeline is processed when this statement applies:
||Stop words are kept if the current
||Stop words acting as query syntax boolean operators are kept (hence