[8.19] [AI Infra] Update NL-2-ESQL docs (#224868)#227186
Merged
qn895 merged 1 commit intoelastic:8.19from Jul 9, 2025
Merged
Conversation
## Summary This PR pulls the latest changes from the Elasticsearch's ES|QL documentation updates the ESQL docs. It also adds new ES|QL docs for: - KQL - TO_DATE_NANOS Test results: ``` Model gpt-4o scored 27.700000000000003 out of 30 ------------------------------------------- ------------------------------------------- Model gpt-4o scores per category - category: ES|QL commands and functions usage - scored 12 out of 13 - category: ES|QL query generation - scored 12.200000000000003 out of 13 - category: SPL to ESQL - scored 3.5 out of 4 ------------------------------------------- Model gpt-4o scored 25.300000000000004 out of 30 ------------------------------------------- ------------------------------------------- Model gpt-4o scores per category - category: ES|QL commands and functions usage - scored 10.3 out of 13 - category: ES|QL query generation - scored 11.500000000000002 out of 13 - category: SPL to ESQL - scored 3.5 out of 4 ------------------------------------------- ------------------------------------------- Model gpt-4o scored 26.300000000000004 out of 30 ------------------------------------------- ------------------------------------------- Model gpt-4o scores per category - category: ES|QL commands and functions usage - scored 10.8 out of 13 - category: ES|QL query generation - scored 11.700000000000003 out of 13 - category: SPL to ESQL - scored 3.8 out of 4 Model gpt-4o scored 27.500000000000004 out of 30 ------------------------------------------- ------------------------------------------- Model gpt-4o scores per category - category: ES|QL commands and functions usage - scored 12 out of 13 - category: ES|QL query generation - scored 11.700000000000003 out of 13 - category: SPL to ESQL - scored 3.8 out of 4 ``` ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> (cherry picked from commit dd29b09)
9 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport
This will backport the following commits from
mainto8.19:Questions ?
Please refer to the Backport tool documentation