-
Notifications
You must be signed in to change notification settings - Fork 25.6k
[Query Rules] clarify query rules API documentation #100732
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Query Rules] clarify query rules API documentation #100732
Conversation
|
Documentation preview: |
|
Pinging @elastic/es-docs (Team:Docs) |
|
Pinging @elastic/ent-search-eng (Team:Enterprise Search) |
|
|
||
| - `my-rule1` will pin documents with IDs `id1` and `id2` when `user.query` exactly matches `marvel` _or_ `dc` **and** `user.country` exactly matches `us`. | ||
| - `my-rule2` will pin documents from different, specified indices with IDs `id3` and `id4` when the `query_string` fuzzily matches `comic`. | ||
| - `my-rule1` will pin documents with IDs `id1` and `id2` when `user_query` contains `pugs` _or_ `puggles` **and** `user_country` exactly matches `us`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why the switch from dot notation here? (e.g. user.query -> user_query)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The feedback was that all of our examples should be consistent. So since we were using user_query everywhere else, it was easier to update this one document over the others.
|
Looks good, but I'll defer to team for technical 👁️ 🔍 |
Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com>
carlosdelest
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
* Update example in query rules docs * Ensure GET docs are also consistent * Update docs/reference/query-rules/apis/put-query-ruleset.asciidoc Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com> --------- Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com>
* Update example in query rules docs * Ensure GET docs are also consistent * Update docs/reference/query-rules/apis/put-query-ruleset.asciidoc Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com> --------- Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com>
* Update example in query rules docs * Ensure GET docs are also consistent * Update docs/reference/query-rules/apis/put-query-ruleset.asciidoc --------- Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com>
* Update example in query rules docs * Ensure GET docs are also consistent * Update docs/reference/query-rules/apis/put-query-ruleset.asciidoc --------- Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com>
We received feedback that different examples of
match_criteriain various parts of the query rules documentation was confusing. This PR streamlines the examples in our query rules documentation (APIs, rule query and search guide).