opensearch-project / opensearch-project/sql
Nested field query 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.
Nested field query is supported by following PartiQL specification: https://github.com/opensearch-project/sql/blob/main/docs/user/beyond/partiql.rst. There are limitations regarding the nested levels and query types that needs improvement.
- https://github.com/opendistro-for-elasticsearch/sql/issues/1055: Comparison between nested field
- https://github.com/opendistro-for-elasticsearch/sql/issues/963: ?
- https://github.com/opendistro-for-elasticsearch/sql/issues/797: Nested field involved in join
- https://github.com/opendistro-for-elasticsearch/sql/issues/399: Select *
- https://github.com/opendistro-for-elasticsearch/sql/issues/398: Aggregate over nested field
- https://github.com/opendistro-for-elasticsearch/sql/issues/245: Nested field involved in join
- https://github.com/opendistro-for-elasticsearch/sql/issues/155: Aggregate over nested field
- https://github.com/opendistro-for-elasticsearch/sql/issues/152: Deep nested field
- https://github.com/opendistro-for-elasticsearch/sql/issues/87: Filter nested field
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 with the PartiQL specification linked in the issue, then review the nine related issues covering nested comparisons, joins, aggregation, selection, filtering, and deep nesting. Define the specific nested query types and nesting levels to improve before identifying the relevant implementation and tests; the issue does not name files or an acceptance criterion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100