opensearch-project / opensearch-project/sql
JOIN support improvement
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 176
- Forks
- 229
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 43
Description
Is your feature request related to a problem? Please describe.
There is limited support for JOIN queries which needs improvement. In particular, post processing such as filtering and aggregation after inner/outer join is most wanted. This capability is required by PPL lookup command.
Here are the feature requests from community:
- https://github.com/opendistro-for-elasticsearch/sql/issues/505: Left join
- https://github.com/opendistro-for-elasticsearch/sql/issues/351: Multi-join
- https://github.com/opendistro-for-elasticsearch/sql/issues/301: Aggregate after join
- https://github.com/opendistro-for-elasticsearch/sql/issues/289: Select function after join
- https://github.com/opendistro-for-elasticsearch/sql/issues/236: Aggregate after join
- https://github.com/opendistro-for-elasticsearch/sql/issues/221: Comma join
- https://github.com/opendistro-for-elasticsearch/sql/issues/124: Left join with WHERE
- https://github.com/opendistro-for-elasticsearch/sql/issues/110: Aggregate after join
- https://github.com/opendistro-for-elasticsearch/sql/issues/987: Multi-join
Describe the solution you'd like
N/A
Describe alternatives you've considered
N/A
Additional context
Add any other context or screenshots about the feature request here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the nine linked JOIN requests, especially the items covering left joins, multi-joins, aggregation, and post-join filtering. The issue names no files, tests, entry points, or defined completion condition, so the scope and acceptance criteria must be clarified before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, sql
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100