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: define interfaces as contractual extension points #119856

Closed
6 tasks done
bpintea opened this issue Jan 9, 2025 · 1 comment
Closed
6 tasks done

ESQL: define interfaces as contractual extension points #119856

bpintea opened this issue Jan 9, 2025 · 1 comment
Labels
:Analytics/ES|QL AKA ESQL >enhancement Meta Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo)

Comments

@bpintea
Copy link
Contributor

bpintea commented Jan 9, 2025

Description

In order to simplify contributions to the ESQL and limit the surface area (and associated mistakes), we should extract common functionality into dedicated interfaces that consumers can choose to implement. This will allow encapsulating new functionality without the new contributions needing to touch core parts.

The following is a list of (initial) interfaces to implement:

@elasticsearchmachine
Copy link
Collaborator

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

@elasticsearchmachine elasticsearchmachine added the Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) label Jan 9, 2025
@bpintea bpintea closed this as completed Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Analytics/ES|QL AKA ESQL >enhancement Meta Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo)
Projects
None yet
Development

No branches or pull requests

2 participants