opensearch-project / opensearch-project/sql
[FEATURE] Enhance patterns command output structure for easy type validation
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?
For now, patterns command outputs a complex structure like MAP(VARCHAR, ANY). New Calcite version has stricter type validation. We should avoid ANY type as much as possible. The goal of this issue is to optimize patterns command output structure type.
What solution would you like?
A clear and concise description of what you want to happen.
What alternatives have you considered?
A clear and concise description of any alternative solutions or features you've considered.
Do you have any 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
The issue names no files, entry points, or tests. Start by locating the patterns command implementation and the tests covering its output type, then inspect where MAP(VARCHAR, ANY) is produced. Define the intended non-ANY structure for stricter Calcite validation and verify the resulting command output with focused tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, sql
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100