Skip to content

ESQL: Fix transport versions #127668

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
May 3, 2025
Merged

Conversation

nik9000
Copy link
Member

@nik9000 nik9000 commented May 2, 2025

In #127623 we backported #127299 and added a backport transport version for it - ESQL_AGGREGATE_METRIC_DOUBLE_BLOCK_8_19 aka 8_841_0_24. This brings that version forwards to main and adds support for parsing streams with that version.

In #127639 we backported #126401 and added a backport transport version for it - PINNED_RETRIEVER_8_19 aka 8_841_0_23. This brings that version forwards to main and adds support for parsing streams with that versions.

In #127633 we a claimed a backport transport version to backport #127314 - INTRODUCE_FAILURES_LIFECYCLE_BACKPORT_8_19 aka 8_841_0_23. That's the same versions as PINNED_RETRIEVER_8_19. It's just that this one is in main and PINNED_RETRIEVER_8_19 is in 8.19. To allow me to bring PINNED_RETRIEVER_8_19 for wards I've had to revert #127633.

Closes #127667

In elastic#127623 we backported elastic#127299 and added a backport transport version
for it - `ESQL_AGGREGATE_METRIC_DOUBLE_BLOCK_8_19` aka `8_841_0_24`.
This brings that version forwards to `main` and adds support for parsing
streams with that version.

In elastic#127639 we backported elastic#126401 and added a backport transport version
for it - `PINNED_RETRIEVER_8_19` aka `8_841_0_23`. This brings that
version forwards to `main` and adds support for parsing streams with
that versions.

In elastic#127633 we a claimed a backport transport version to backport elastic#127314 -
`INTRODUCE_FAILURES_LIFECYCLE_BACKPORT_8_19` aka `8_841_0_23`. That's
the same versions as `PINNED_RETRIEVER_8_19`. It's just that this one is
in `main` and `PINNED_RETRIEVER_8_19` is in `8.19`. To allow me to bring
`PINNED_RETRIEVER_8_19` for wards I've had to revert elastic#127633.

Closes elastic#127667
@nik9000 nik9000 added >bug :Data Management/Data streams Data streams and their lifecycles :Analytics/ES|QL AKA ESQL :SearchOrg/Relevance Label for the Search (solution/org) Relevance team v9.1.0 labels May 2, 2025
@nik9000 nik9000 added the auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) label May 2, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-analytical-engine (Team:Analytics)

@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/search-eng (Team:SearchOrg)

@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/search-relevance (Team:Search - Relevance)

@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-data-management (Team:Data Management)

@elasticsearchmachine
Copy link
Collaborator

Hi @nik9000, I've created a changelog YAML for you.

@nik9000
Copy link
Member Author

nik9000 commented May 2, 2025

I'm marking this as auto-merge-without-approval because main can't get more broken at the moment.

Copy link
Member

@dnhatn dnhatn left a comment

Choose a reason for hiding this comment

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

@nik9000 Thank you so much for fixing this.

@elasticsearchmachine elasticsearchmachine merged commit 2acd563 into elastic:main May 3, 2025
17 checks passed
@nik9000 nik9000 deleted the pick_up_version branch May 3, 2025 01:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Analytics/ES|QL AKA ESQL auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) >bug :Data Management/Data streams Data streams and their lifecycles :SearchOrg/Relevance Label for the Search (solution/org) Relevance team v9.1.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Transport versions are mixed up
3 participants