[DOCS] Rewrite terms_set query
#43060
Conversation
jrodewig
added
>docs
|
Pinging @elastic/es-search |
There was a problem hiding this comment.
Thanks again @jrodewig, I didn't know this query very well and it was a pleasure reading the rewrite. Left one suggestions regarding "boost" again, also I wasn't sure about real-life use cases for this type of query so I did a bit of digging when/why this was added and found #26915. There are two more or less intuitive examples where this pretty specialized query might be useful in #26915 (comment). I don't know how far you want to take details in these reference docs but maybe there is a way of including some of these thoughts succinctly? Just an idea, maybe that makes the docs to complicated so I leave it up to you.
|
|
||
| An example that always limits the number of required terms to match to never | ||
| become larger than the number of terms specified: | ||
| `boost`:: |
There was a problem hiding this comment.
Like in a previous PR, maybe we could mention the "boost" parameter on all queries for completeness but link to a common paragraph for the detailed discussion.
|
Thanks for the review and praise @cbuescher. I've updated the example and included the listed use cases with a33ee6e. Thanks for pointing out #26915. I feel like the examples are much more practical now. I also removed the |
Changes
terms_setqueryThis is part of #40977, an effort to standardize documentation for query types.
Before
Before image
After
After image