[ES|QL] Moves fork in tech preview#224680
Merged
stratoula merged 3 commits intoelastic:mainfrom Jun 23, 2025
Merged
Conversation
13 tasks
Contributor
|
Pinging @elastic/kibana-esql (Team:ESQL) |
Contributor
💚 Build Succeeded
Metrics [docs]Page load bundle
History
|
Contributor
|
Starting backport for target branches: 8.19 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Jun 23, 2025
## Summary Moves the fork command on tech preview <img width="878" alt="image" src="https://github.com/user-attachments/assets/d21d593d-f157-45e4-94aa-c97d5f3098ca" /> It also enables all the processing commands in the autocomplete except for enrich, mostly because the client side validation complains. As enrich is considered kinda deprecated I think it is ok to skip the suggestion. I will create an issue to track the client side validation problem though (Update: Added in [client side validation bugs](elastic#192255 (comment))) ### Checklist - [ ] [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 (cherry picked from commit 7c2ac23)
Contributor
💚 All backports created successfully
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
Jun 23, 2025
# Backport This will backport the following commits from `main` to `8.19`: - [[ES|QL] Moves fork in tech preview (#224680)](#224680) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Stratoula Kalafateli","email":"efstratia.kalafateli@elastic.co"},"sourceCommit":{"committedDate":"2025-06-23T07:30:12Z","message":"[ES|QL] Moves fork in tech preview (#224680)\n\n## Summary\n\nMoves the fork command on tech preview\n\n<img width=\"878\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/d21d593d-f157-45e4-94aa-c97d5f3098ca\"\n/>\n\nIt also enables all the processing commands in the autocomplete except\nfor enrich, mostly because the client side validation complains. As\nenrich is considered kinda deprecated I think it is ok to skip the\nsuggestion. I will create an issue to track the client side validation\nproblem though (Update: Added in [client side validation\nbugs](https://github.com/elastic/kibana/issues/192255#issuecomment-2991343277))\n\n### Checklist\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","sha":"7c2ac235ef8d1c46dd82403130789a7c671f3ae5","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Feature:ES|QL","Team:ESQL","backport:version","v9.1.0","v8.19.0"],"title":"[ES|QL] Moves fork in tech preview","number":224680,"url":"https://github.com/elastic/kibana/pull/224680","mergeCommit":{"message":"[ES|QL] Moves fork in tech preview (#224680)\n\n## Summary\n\nMoves the fork command on tech preview\n\n<img width=\"878\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/d21d593d-f157-45e4-94aa-c97d5f3098ca\"\n/>\n\nIt also enables all the processing commands in the autocomplete except\nfor enrich, mostly because the client side validation complains. As\nenrich is considered kinda deprecated I think it is ok to skip the\nsuggestion. I will create an issue to track the client side validation\nproblem though (Update: Added in [client side validation\nbugs](https://github.com/elastic/kibana/issues/192255#issuecomment-2991343277))\n\n### Checklist\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","sha":"7c2ac235ef8d1c46dd82403130789a7c671f3ae5"}},"sourceBranch":"main","suggestedTargetBranches":["8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/224680","number":224680,"mergeCommit":{"message":"[ES|QL] Moves fork in tech preview (#224680)\n\n## Summary\n\nMoves the fork command on tech preview\n\n<img width=\"878\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/d21d593d-f157-45e4-94aa-c97d5f3098ca\"\n/>\n\nIt also enables all the processing commands in the autocomplete except\nfor enrich, mostly because the client side validation complains. As\nenrich is considered kinda deprecated I think it is ok to skip the\nsuggestion. I will create an issue to track the client side validation\nproblem though (Update: Added in [client side validation\nbugs](https://github.com/elastic/kibana/issues/192255#issuecomment-2991343277))\n\n### Checklist\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","sha":"7c2ac235ef8d1c46dd82403130789a7c671f3ae5"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>
akowalska622
pushed a commit
to akowalska622/kibana
that referenced
this pull request
Jun 25, 2025
## Summary Moves the fork command on tech preview <img width="878" alt="image" src="https://github.com/user-attachments/assets/d21d593d-f157-45e4-94aa-c97d5f3098ca" /> It also enables all the processing commands in the autocomplete except for enrich, mostly because the client side validation complains. As enrich is considered kinda deprecated I think it is ok to skip the suggestion. I will create an issue to track the client side validation problem though (Update: Added in [client side validation bugs](elastic#192255 (comment))) ### Checklist - [ ] [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
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
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.
Summary
Moves the fork command on tech preview
It also enables all the processing commands in the autocomplete except for enrich, mostly because the client side validation complains. As enrich is considered kinda deprecated I think it is ok to skip the suggestion. I will create an issue to track the client side validation problem though (Update: Added in client side validation bugs)
Checklist