Skip to content
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

ESQL: Remove historical features #116966

Merged
merged 4 commits into from
Nov 21, 2024
Merged

Conversation

nik9000
Copy link
Member

@nik9000 nik9000 commented Nov 18, 2024

Our friends working on cluster features are looking to remove the infrastructure for historical features. In main all historical features are always enabled because historical features weren't allowed to support versions before 8.a_long_time_ago. All of ours are certainly enabled for versions main is wire compatible with.

Our friends working on cluster features are looking to remove the
infrastructure for historical features. In `main` all historical
features are always enabled because historical features weren't allowed
to support versions before 8.a_long_time_ago. All of ours are certainly
enabled for versions `main` is wire compatible with.
@nik9000 nik9000 requested a review from thecoop November 18, 2024 16:22
@elasticsearchmachine elasticsearchmachine added the Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) label Nov 18, 2024
@elasticsearchmachine
Copy link
Collaborator

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

Copy link
Member

@thecoop thecoop left a comment

Choose a reason for hiding this comment

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

Thanks!

Copy link
Contributor

@alex-spies alex-spies left a comment

Choose a reason for hiding this comment

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

LGTM in terms of ESQL, this should be safe to do.

// not all nodes in the cluster have upgraded to esql - just use this node for now
return new DiscoveryNode[] { clusterService.localNode() };
}
return super.resolveRequest(request, clusterState);
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we even need the override if we defer to super?

Copy link
Member Author

Choose a reason for hiding this comment

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

Er, nope. sorry. Was being too quick on the refactor.

@nik9000 nik9000 merged commit 06840ba into elastic:main Nov 21, 2024
16 checks passed
alexey-ivanov-es pushed a commit to alexey-ivanov-es/elasticsearch that referenced this pull request Nov 28, 2024
Our friends working on cluster features are looking to remove the
infrastructure for historical features. In `main` all historical
features are always enabled because historical features weren't allowed
to support versions before 8.a_long_time_ago. All of ours are certainly
enabled for versions `main` is wire compatible with.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Analytics/ES|QL AKA ESQL >non-issue Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) v9.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants