Skip to content

Commit dc49367

Browse files
tklarsenVesaJuvonen
authored andcommitted
Update info about XRANK (SharePoint#1823)
Add info about potential effect on performance
1 parent a09ed62 commit dc49367

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

docs/general-development/keyword-query-language-kql-syntax-reference.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -561,7 +561,8 @@ You can specify whether the results that are returned should include or exclude
561561

562562
You use the **XRANK** operator to boost the dynamic rank of items based on certain term occurrences within the _match expression_, without changing which items match the query. An **XRANK** expression contains one component that must be matched, the _match expression_, and one or more components that contribute only to dynamic ranking, the _rank expression_. At least **one** of the parameters, excluding _n_, must be specified for an **XRANK** expression to be valid.
563563

564-
564+
> [!NOTE]
565+
> Query latency (and probability of timeout) increases when using complex queries and especially when using xrank operators. The increase in query latency depends on the number of **XRANK** operators and the number of hits in the _match expression_ and _rank expression_ components in the query tree.
565566
566567
_Match expressions_ may be any valid KQL expression, including nested **XRANK** expressions. _Rank expressions_ may be any valid KQL expression without **XRANK** expressions. If your KQL queries have multiple **XRANK** operators, the final dynamic rank value is calculated as a sum of boosts across all **XRANK** operators.
567568

0 commit comments

Comments
 (0)