Conversation
Param order addressed, adding reference to MV_INTERSECTS for any vs all semantics.
🔍 Preview links for changed docs⏳ Building and deploying preview... View progress This comment will be updated with preview links when the build is complete. |
✅ Vale Linting ResultsNo issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
|
#5684 already addresses the param order. |
|
|
||
| 2. When defining the control, select the **Allow multiple selections** option. | ||
| :::{note} | ||
| [`MV_CONTAINS`](elasticsearch://reference/query-languages/esql/functions-operators/mv-functions/mv_contains.md) will check if _all_ values are present, use [`MV_INTERSECTS`](elasticsearch://reference/query-languages/esql/functions-operators/mv-functions/mv_intersects.md) if you want _any_ present semantics. |
There was a problem hiding this comment.
| [`MV_CONTAINS`](elasticsearch://reference/query-languages/esql/functions-operators/mv-functions/mv_contains.md) will check if _all_ values are present, use [`MV_INTERSECTS`](elasticsearch://reference/query-languages/esql/functions-operators/mv-functions/mv_intersects.md) if you want _any_ present semantics. | |
| [`MV_CONTAINS`](elasticsearch://reference/query-languages/esql/functions-operators/mv-functions/mv_contains.md) checks that _all_ subset values are present. Use [`MV_INTERSECTS`](elasticsearch://reference/query-languages/esql/functions-operators/mv-functions/mv_intersects.md) instead if matching _any_ subset value is enough. |
minor suggestion to tighten up language—it's not perfect just felt the final sentence was a bit jargony and could be more concrete :)
|
Hey, @mjmbischoff, thanks for the addition there. Since this section is explicitly about how to enable variable controls that can accept multiple values, are we saying that MV_INTERSECTS now also allows this? My initial understanding was that only MV_CONTAINS allowed this (unless there has been some recent development I haven't caught up on yet). CC @stratoula can you confirm? |
|
|
||
| 2. When defining the control, select the **Allow multiple selections** option. | ||
| :::{note} | ||
| [`MV_CONTAINS`](elasticsearch://reference/query-languages/esql/functions-operators/mv-functions/mv_contains.md) will check if _all_ values are present, use [`MV_INTERSECTS`](elasticsearch://reference/query-languages/esql/functions-operators/mv-functions/mv_intersects.md) if you want _any_ present semantics. |
There was a problem hiding this comment.
Hey! Can you explain to me which is the difference between MV_CONTAINS with the MV_INTERSECTS we want to add here?
4 participants
Summary
Param order addressed(otherwise docs with null value in field are always returned), adding reference to MV_INTERSECTS for any vs all semantics.
Generative AI disclosure