Skip to content

Conversation

@qn895
Copy link
Member

@qn895 qn895 commented Jan 4, 2025

Closes #188978
Closes #199092

This PR addresses #199092 and adds automated script to sync operators and adds support for MATCH and its equivalent : match operator.

Screen.Recording.2025-01-17.at.15.36.30.mov
Screen.Recording.2025-01-17.at.15.36.11.mov

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, uses sentence case text and includes i18n support
  • Documentation was added for features that require explanation or tutorials
  • Unit or functional tests 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
  • 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 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

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.

@qn895
Copy link
Member Author

qn895 commented Jan 4, 2025

/ci

@qn895
Copy link
Member Author

qn895 commented Jan 5, 2025

/ci

@qn895 qn895 self-assigned this Jan 6, 2025
@qn895 qn895 added v9.0.0 Team:ESQL ES|QL related features in Kibana t// labels Jan 6, 2025
@qn895 qn895 requested a review from stratoula January 7, 2025 15:37
Copy link
Contributor

@stratoula stratoula left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanx Quynh! I didnt test it but I have some questions to understand better the code. Also why do I see changes in the validation tests?

}));
}

const leftHandSideParamName = new Set(['left', 'field', 'lhs']);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Haven't we mapped in the script above as left? Why do we need them here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point! This was a left over. I removed it here 9f938ef (#205565)

str !== 'unsupported' &&
(dataTypes.includes(str as SupportedDataType) || str === 'unknown' || str === 'any');

export interface Signature {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!

"query": "row 1 years + 1 year",
"error": [
"Argument of [+] must be [date], found value [1 years] type [duration]"
"Argument of [+] must be [date], found value [1 year] type [duration]"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So now we start the validation from the end and not from the beginning?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@qn895 can you explain to me these changes here?

extraSignatures?: Signature[];
}
> = {
add: {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So every time a new operator is being added we need to add an entry here? Can this info be given by ES? Have we talked with them?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have you discussed this with Nik?

].map((op): FunctionDefinition => createComparisonDefinition(op));

const likeFunctions: FunctionDefinition[] = [
const notLikeFunctions: FunctionDefinition[] = [
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I dont understand this change, the not_like is not being returned from ES?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I left this notLikeFunctions here cause I didn't see an equivalent from Elasticsearch.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we ask them to add them ? (if you haven't done already)

@qn895
Copy link
Member Author

qn895 commented Jan 13, 2025

/ci

@stratoula
Copy link
Contributor

@qn895 lets run the script when this PR gets merged elastic/elasticsearch#120504 which addresses the like and rlike operators.

@qn895 qn895 added the v8.18.0 label Jan 23, 2025
Copy link
Contributor

@stratoula stratoula left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@stratoula stratoula added release_note:skip Skip the PR/issue when compiling release notes and removed release_note:feature Makes this part of the condensed release notes labels Jan 28, 2025
@qn895
Copy link
Member Author

qn895 commented Jan 28, 2025

For #205565 (files), in this case, this is coming from one of the Elasticsearch-generated signatures for add, which is more robust than what we had previously:


    {
      params: [
        {
          name: 'left',
          type: 'time_duration',
          optional: false,
        },
        {
          name: 'right',
          type: 'date_nanos',
          optional: false,
        },
      ],
      returnType: 'date_nanos',
    },

The validation goes from left to right, meaning it depends on what was previously typed before the operator. In this case, after 1 years +, it expects date type. I think it makes sense this way and instead of the previous way?

For #205565 (files), I'll investigate a bit more after FF (if possible) how to remove this meta completely by adding more info on the ES side. Some of the changes we need from ES are straightforward, but there's a few pieces in the current implementation that requires some rewiring.

# Conflicts:
#	src/platform/packages/shared/kbn-esql-validation-autocomplete/src/shared/constants.ts
@elasticmachine
Copy link
Contributor

💚 Build Succeeded

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id before after diff
cloudSecurityPosture 774 775 +1
controls 472 473 +1
dashboard 746 747 +1
data 607 608 +1
dataVisualizer 816 817 +1
discover 1070 1071 +1
esql 210 211 +1
esqlDataGrid 499 500 +1
eventAnnotationListing 739 740 +1
infra 1301 1302 +1
investigateApp 666 667 +1
lens 1796 1797 +1
lists 430 431 +1
logsExplorer 696 697 +1
maps 1334 1335 +1
ml 2201 2202 +1
observability 1351 1352 +1
observabilityAIAssistantApp 504 505 +1
securitySolution 6593 6594 +1
slo 983 984 +1
stackAlerts 270 271 +1
unifiedHistogram 282 283 +1
unifiedSearch 392 393 +1
total +23

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id before after diff
@kbn/esql-validation-autocomplete 204 205 +1

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
securitySolution 21.3MB 21.3MB +42.7KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id before after diff
kbnUiSharedDeps-srcJs 3.5MB 3.6MB +43.3KB
Unknown metric groups

API count

id before after diff
@kbn/esql-validation-autocomplete 216 217 +1

History

cc @qn895

@stratoula
Copy link
Contributor

@qn895

The validation goes from left to right, meaning it depends on what was previously typed before the operator. In this case, after 1 years +, it expects date type. I think it makes sense this way and instead of the previous way?

Ah I see now, this is much better yes 👍

I'll investigate a bit more after FF (if possible) how to remove this meta completely by adding more info on the ES side. Some of the changes we need from ES are straightforward, but there's a few pieces in the current implementation that requires some rewiring.

Sure it will be cool if we can remove this section. 🙏

@stratoula stratoula merged commit 6fed083 into elastic:main Jan 29, 2025
9 checks passed
@kibanamachine
Copy link
Contributor

Starting backport for target branches: 8.x

https://github.com/elastic/kibana/actions/runs/13026734780

kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Jan 29, 2025
…TCH operators (elastic#205565)

Closes elastic#188978
Closes elastic#199092

This PR addresses elastic#199092 and
adds automated script to sync operators and adds support for MATCH and
its equivalent `:` match operator.

https://github.com/user-attachments/assets/8f78345d-f1a0-4be4-8eba-2aae35225842

https://github.com/user-attachments/assets/eb9e63e3-0086-45a5-b782-199225895afc

### 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/packages/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: Stratoula Kalafateli <[email protected]>
Co-authored-by: Elastic Machine <[email protected]>
(cherry picked from commit 6fed083)
@kibanamachine
Copy link
Contributor

💚 All backports created successfully

Status Branch Result
8.x

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

kibanamachine added a commit that referenced this pull request Jan 29, 2025
…for MATCH operators (#205565) (#208678)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[ES|QL] Add automated script to sync operators and add support for
MATCH operators
(#205565)](#205565)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Quynh Nguyen
(Quinn)","email":"[email protected]"},"sourceCommit":{"committedDate":"2025-01-29T07:45:35Z","message":"[ES|QL]
Add automated script to sync operators and add support for MATCH
operators (#205565)\n\nCloses
https://github.com/elastic/kibana/issues/188978\nCloses
https://github.com/elastic/kibana/issues/199092\n\nThis PR addresses
#199092 and\nadds automated
script to sync operators and adds support for MATCH and\nits equivalent
`:` match
operator.\n\n\nhttps://github.com/user-attachments/assets/8f78345d-f1a0-4be4-8eba-2aae35225842\n\n\n\nhttps://github.com/user-attachments/assets/eb9e63e3-0086-45a5-b782-199225895afc\n\n\n
\n\n### Checklist\n\nCheck the PR satisfies following conditions.
\n\nReviewers should verify this PR satisfies this list as well.\n\n- [
] Any text added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n###
Identify risks\n\nDoes this PR introduce any risks? For example,
consider risks like hard\nto test bugs, performance regression,
potential of data loss.\n\nDescribe the risk, its severity, and
mitigation for each identified\nrisk. Invite stakeholders and evaluate
how to proceed before merging.\n\n- [ ] [See some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ] ...\n\n---------\n\nCo-authored-by: Stratoula Kalafateli
<[email protected]>\nCo-authored-by: Elastic Machine
<[email protected]>","sha":"6fed08348c2d8faba72f27220fb5ba475df292ac","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Feature:ES|QL","Team:ESQL","backport:version","v8.18.0"],"title":"[ES|QL]
Add automated script to sync operators and add support for MATCH
operators","number":205565,"url":"https://github.com/elastic/kibana/pull/205565","mergeCommit":{"message":"[ES|QL]
Add automated script to sync operators and add support for MATCH
operators (#205565)\n\nCloses
https://github.com/elastic/kibana/issues/188978\nCloses
https://github.com/elastic/kibana/issues/199092\n\nThis PR addresses
#199092 and\nadds automated
script to sync operators and adds support for MATCH and\nits equivalent
`:` match
operator.\n\n\nhttps://github.com/user-attachments/assets/8f78345d-f1a0-4be4-8eba-2aae35225842\n\n\n\nhttps://github.com/user-attachments/assets/eb9e63e3-0086-45a5-b782-199225895afc\n\n\n
\n\n### Checklist\n\nCheck the PR satisfies following conditions.
\n\nReviewers should verify this PR satisfies this list as well.\n\n- [
] Any text added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n###
Identify risks\n\nDoes this PR introduce any risks? For example,
consider risks like hard\nto test bugs, performance regression,
potential of data loss.\n\nDescribe the risk, its severity, and
mitigation for each identified\nrisk. Invite stakeholders and evaluate
how to proceed before merging.\n\n- [ ] [See some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ] ...\n\n---------\n\nCo-authored-by: Stratoula Kalafateli
<[email protected]>\nCo-authored-by: Elastic Machine
<[email protected]>","sha":"6fed08348c2d8faba72f27220fb5ba475df292ac"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/205565","number":205565,"mergeCommit":{"message":"[ES|QL]
Add automated script to sync operators and add support for MATCH
operators (#205565)\n\nCloses
https://github.com/elastic/kibana/issues/188978\nCloses
https://github.com/elastic/kibana/issues/199092\n\nThis PR addresses
#199092 and\nadds automated
script to sync operators and adds support for MATCH and\nits equivalent
`:` match
operator.\n\n\nhttps://github.com/user-attachments/assets/8f78345d-f1a0-4be4-8eba-2aae35225842\n\n\n\nhttps://github.com/user-attachments/assets/eb9e63e3-0086-45a5-b782-199225895afc\n\n\n
\n\n### Checklist\n\nCheck the PR satisfies following conditions.
\n\nReviewers should verify this PR satisfies this list as well.\n\n- [
] Any text added follows [EUI's
writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\nsentence case text and includes
[i18n\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\n-
[
]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas
added for features that require explanation or tutorials\n- [ ] [Unit or
functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere
updated or added to match the most common scenarios\n- [ ] If a plugin
configuration key changed, check if it needs to be\nallowlisted in the
cloud and added to the
[docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n-
[ ] This was checked for breaking HTTP API changes, and any
breaking\nchanges have been approved by the breaking-change committee.
The\n`release_note:breaking` label should be applied in these
situations.\n- [ ] [Flaky
Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)
was\nused on any tests changed\n- [ ] The PR description includes the
appropriate Release Notes section,\nand the correct `release_note:*`
label is applied per
the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n###
Identify risks\n\nDoes this PR introduce any risks? For example,
consider risks like hard\nto test bugs, performance regression,
potential of data loss.\n\nDescribe the risk, its severity, and
mitigation for each identified\nrisk. Invite stakeholders and evaluate
how to proceed before merging.\n\n- [ ] [See some
risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n-
[ ] ...\n\n---------\n\nCo-authored-by: Stratoula Kalafateli
<[email protected]>\nCo-authored-by: Elastic Machine
<[email protected]>","sha":"6fed08348c2d8faba72f27220fb5ba475df292ac"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Quynh Nguyen (Quinn) <[email protected]>
drewdaemon added a commit that referenced this pull request Mar 31, 2025
## Summary

in #205565 we accidentally removed
the behavior where we don't show `NOT LIKE` and `NOT RLIKE` in the
suggestions list. We want to show these eventually but right now, it's
broken behavior:



https://github.com/user-attachments/assets/0a7f860d-3a12-49cf-94b3-668848cff6ae

---------

Co-authored-by: Stratoula Kalafateli <[email protected]>
Co-authored-by: Elastic Machine <[email protected]>
kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Mar 31, 2025
## Summary

in elastic#205565 we accidentally removed
the behavior where we don't show `NOT LIKE` and `NOT RLIKE` in the
suggestions list. We want to show these eventually but right now, it's
broken behavior:

https://github.com/user-attachments/assets/0a7f860d-3a12-49cf-94b3-668848cff6ae

---------

Co-authored-by: Stratoula Kalafateli <[email protected]>
Co-authored-by: Elastic Machine <[email protected]>
(cherry picked from commit 4970bb9)
drewdaemon added a commit to drewdaemon/kibana that referenced this pull request Mar 31, 2025
## Summary

in elastic#205565 we accidentally removed
the behavior where we don't show `NOT LIKE` and `NOT RLIKE` in the
suggestions list. We want to show these eventually but right now, it's
broken behavior:

https://github.com/user-attachments/assets/0a7f860d-3a12-49cf-94b3-668848cff6ae

---------

Co-authored-by: Stratoula Kalafateli <[email protected]>
Co-authored-by: Elastic Machine <[email protected]>
(cherry picked from commit 4970bb9)

# Conflicts:
#	src/platform/packages/shared/kbn-esql-validation-autocomplete/src/definitions/generated/operators.ts
drewdaemon added a commit to drewdaemon/kibana that referenced this pull request Mar 31, 2025
## Summary

in elastic#205565 we accidentally removed
the behavior where we don't show `NOT LIKE` and `NOT RLIKE` in the
suggestions list. We want to show these eventually but right now, it's
broken behavior:

https://github.com/user-attachments/assets/0a7f860d-3a12-49cf-94b3-668848cff6ae

---------

Co-authored-by: Stratoula Kalafateli <[email protected]>
Co-authored-by: Elastic Machine <[email protected]>
(cherry picked from commit 4970bb9)

# Conflicts:
#	src/platform/packages/shared/kbn-esql-validation-autocomplete/src/definitions/generated/operators.ts
kibanamachine added a commit that referenced this pull request Mar 31, 2025
…216533)

# Backport

This will backport the following commits from `main` to `8.x`:
- [[ES|QL] Hide "not" operators from suggestions menu
(#216355)](#216355)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Drew
Tate","email":"[email protected]"},"sourceCommit":{"committedDate":"2025-03-31T19:25:08Z","message":"[ES|QL]
Hide \"not\" operators from suggestions menu (#216355)\n\n##
Summary\n\nin #205565 we
accidentally removed\nthe behavior where we don't show `NOT LIKE` and
`NOT RLIKE` in the\nsuggestions list. We want to show these eventually
but right now, it's\nbroken
behavior:\n\n\n\nhttps://github.com/user-attachments/assets/0a7f860d-3a12-49cf-94b3-668848cff6ae\n\n---------\n\nCo-authored-by:
Stratoula Kalafateli <[email protected]>\nCo-authored-by:
Elastic Machine
<[email protected]>","sha":"4970bb95ccb99b7cedfde51a3f4d56906607e28d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Feature:ES|QL","Team:ESQL","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[ES|QL]
Hide \"not\" operators from suggestions
menu","number":216355,"url":"https://github.com/elastic/kibana/pull/216355","mergeCommit":{"message":"[ES|QL]
Hide \"not\" operators from suggestions menu (#216355)\n\n##
Summary\n\nin #205565 we
accidentally removed\nthe behavior where we don't show `NOT LIKE` and
`NOT RLIKE` in the\nsuggestions list. We want to show these eventually
but right now, it's\nbroken
behavior:\n\n\n\nhttps://github.com/user-attachments/assets/0a7f860d-3a12-49cf-94b3-668848cff6ae\n\n---------\n\nCo-authored-by:
Stratoula Kalafateli <[email protected]>\nCo-authored-by:
Elastic Machine
<[email protected]>","sha":"4970bb95ccb99b7cedfde51a3f4d56906607e28d"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216355","number":216355,"mergeCommit":{"message":"[ES|QL]
Hide \"not\" operators from suggestions menu (#216355)\n\n##
Summary\n\nin #205565 we
accidentally removed\nthe behavior where we don't show `NOT LIKE` and
`NOT RLIKE` in the\nsuggestions list. We want to show these eventually
but right now, it's\nbroken
behavior:\n\n\n\nhttps://github.com/user-attachments/assets/0a7f860d-3a12-49cf-94b3-668848cff6ae\n\n---------\n\nCo-authored-by:
Stratoula Kalafateli <[email protected]>\nCo-authored-by:
Elastic Machine
<[email protected]>","sha":"4970bb95ccb99b7cedfde51a3f4d56906607e28d"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Drew Tate <[email protected]>
cqliu1 pushed a commit to cqliu1/kibana that referenced this pull request Mar 31, 2025
## Summary

in elastic#205565 we accidentally removed
the behavior where we don't show `NOT LIKE` and `NOT RLIKE` in the
suggestions list. We want to show these eventually but right now, it's
broken behavior:



https://github.com/user-attachments/assets/0a7f860d-3a12-49cf-94b3-668848cff6ae

---------

Co-authored-by: Stratoula Kalafateli <[email protected]>
Co-authored-by: Elastic Machine <[email protected]>
drewdaemon added a commit that referenced this pull request Apr 1, 2025
…216548)

# Backport

This will backport the following commits from `main` to `8.18`:
- [[ES|QL] Hide "not" operators from suggestions menu
(#216355)](#216355)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Drew
Tate","email":"[email protected]"},"sourceCommit":{"committedDate":"2025-03-31T19:25:08Z","message":"[ES|QL]
Hide \"not\" operators from suggestions menu (#216355)\n\n##
Summary\n\nin #205565 we
accidentally removed\nthe behavior where we don't show `NOT LIKE` and
`NOT RLIKE` in the\nsuggestions list. We want to show these eventually
but right now, it's\nbroken
behavior:\n\n\n\nhttps://github.com/user-attachments/assets/0a7f860d-3a12-49cf-94b3-668848cff6ae\n\n---------\n\nCo-authored-by:
Stratoula Kalafateli <[email protected]>\nCo-authored-by:
Elastic Machine
<[email protected]>","sha":"4970bb95ccb99b7cedfde51a3f4d56906607e28d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Feature:ES|QL","Team:ESQL","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[ES|QL]
Hide \"not\" operators from suggestions
menu","number":216355,"url":"https://github.com/elastic/kibana/pull/216355","mergeCommit":{"message":"[ES|QL]
Hide \"not\" operators from suggestions menu (#216355)\n\n##
Summary\n\nin #205565 we
accidentally removed\nthe behavior where we don't show `NOT LIKE` and
`NOT RLIKE` in the\nsuggestions list. We want to show these eventually
but right now, it's\nbroken
behavior:\n\n\n\nhttps://github.com/user-attachments/assets/0a7f860d-3a12-49cf-94b3-668848cff6ae\n\n---------\n\nCo-authored-by:
Stratoula Kalafateli <[email protected]>\nCo-authored-by:
Elastic Machine
<[email protected]>","sha":"4970bb95ccb99b7cedfde51a3f4d56906607e28d"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216355","number":216355,"mergeCommit":{"message":"[ES|QL]
Hide \"not\" operators from suggestions menu (#216355)\n\n##
Summary\n\nin #205565 we
accidentally removed\nthe behavior where we don't show `NOT LIKE` and
`NOT RLIKE` in the\nsuggestions list. We want to show these eventually
but right now, it's\nbroken
behavior:\n\n\n\nhttps://github.com/user-attachments/assets/0a7f860d-3a12-49cf-94b3-668848cff6ae\n\n---------\n\nCo-authored-by:
Stratoula Kalafateli <[email protected]>\nCo-authored-by:
Elastic Machine
<[email protected]>","sha":"4970bb95ccb99b7cedfde51a3f4d56906607e28d"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/216533","number":216533,"state":"OPEN"}]}]
BACKPORT-->
drewdaemon added a commit that referenced this pull request Apr 1, 2025
…216544)

# Backport

This will backport the following commits from `main` to `9.0`:
- [[ES|QL] Hide "not" operators from suggestions menu
(#216355)](#216355)

<!--- Backport version: 9.6.6 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sorenlouv/backport)

<!--BACKPORT [{"author":{"name":"Drew
Tate","email":"[email protected]"},"sourceCommit":{"committedDate":"2025-03-31T19:25:08Z","message":"[ES|QL]
Hide \"not\" operators from suggestions menu (#216355)\n\n##
Summary\n\nin #205565 we
accidentally removed\nthe behavior where we don't show `NOT LIKE` and
`NOT RLIKE` in the\nsuggestions list. We want to show these eventually
but right now, it's\nbroken
behavior:\n\n\n\nhttps://github.com/user-attachments/assets/0a7f860d-3a12-49cf-94b3-668848cff6ae\n\n---------\n\nCo-authored-by:
Stratoula Kalafateli <[email protected]>\nCo-authored-by:
Elastic Machine
<[email protected]>","sha":"4970bb95ccb99b7cedfde51a3f4d56906607e28d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Feature:ES|QL","Team:ESQL","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[ES|QL]
Hide \"not\" operators from suggestions
menu","number":216355,"url":"https://github.com/elastic/kibana/pull/216355","mergeCommit":{"message":"[ES|QL]
Hide \"not\" operators from suggestions menu (#216355)\n\n##
Summary\n\nin #205565 we
accidentally removed\nthe behavior where we don't show `NOT LIKE` and
`NOT RLIKE` in the\nsuggestions list. We want to show these eventually
but right now, it's\nbroken
behavior:\n\n\n\nhttps://github.com/user-attachments/assets/0a7f860d-3a12-49cf-94b3-668848cff6ae\n\n---------\n\nCo-authored-by:
Stratoula Kalafateli <[email protected]>\nCo-authored-by:
Elastic Machine
<[email protected]>","sha":"4970bb95ccb99b7cedfde51a3f4d56906607e28d"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/216355","number":216355,"mergeCommit":{"message":"[ES|QL]
Hide \"not\" operators from suggestions menu (#216355)\n\n##
Summary\n\nin #205565 we
accidentally removed\nthe behavior where we don't show `NOT LIKE` and
`NOT RLIKE` in the\nsuggestions list. We want to show these eventually
but right now, it's\nbroken
behavior:\n\n\n\nhttps://github.com/user-attachments/assets/0a7f860d-3a12-49cf-94b3-668848cff6ae\n\n---------\n\nCo-authored-by:
Stratoula Kalafateli <[email protected]>\nCo-authored-by:
Elastic Machine
<[email protected]>","sha":"4970bb95ccb99b7cedfde51a3f4d56906607e28d"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/216533","number":216533,"state":"OPEN"}]}]
BACKPORT-->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport:version Backport to applied version labels Feature:ES|QL ES|QL related features in Kibana release_note:skip Skip the PR/issue when compiling release notes Team:ESQL ES|QL related features in Kibana t// v8.18.0 v9.0.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[ES|QL] Add match operator support in the editor [ES|QL] automatically sync operator definitions and docs

4 participants