fd9d7335c8
Since Kibana only needs CCS metadata in ESQL responses from certain well-defined locations, we are making CCS metadata opt-in. This feature is patterned after ESQL profiling, where you specify "profile": true in the ESQL body and if you asked for it will be present in the response always (it will be written to the .async-search index and you can’t turn it off in later async-search requests against this particular query ID) and if you didn’t ask for it at the beginning it will never be present (it will NOT be written to the .async-search index when it is persisted). The new option is "include_ccs_metadata": true/false. |
||
|---|---|---|
| .. | ||
| functions | ||
| processing-commands | ||
| source-commands | ||
| esql-across-clusters.asciidoc | ||
| esql-apis.asciidoc | ||
| esql-async-query-api.asciidoc | ||
| esql-async-query-delete-api.asciidoc | ||
| esql-async-query-get-api.asciidoc | ||
| esql-commands.asciidoc | ||
| esql-enrich-data.asciidoc | ||
| esql-examples.asciidoc | ||
| esql-functions-operators.asciidoc | ||
| esql-get-started.asciidoc | ||
| esql-kibana.asciidoc | ||
| esql-language.asciidoc | ||
| esql-limitations.asciidoc | ||
| esql-multi-index.asciidoc | ||
| esql-process-data-with-dissect-grok.asciidoc | ||
| esql-query-api.asciidoc | ||
| esql-rest.asciidoc | ||
| esql-security-solution.asciidoc | ||
| esql-syntax.asciidoc | ||
| esql-using.asciidoc | ||
| implicit-casting.asciidoc | ||
| index.asciidoc | ||
| metadata-fields.asciidoc | ||
| multivalued-fields.asciidoc | ||
| task-management.asciidoc | ||