opensearch-project / opensearch-project/sql

[FEATURE] Support more opensearch data types, like ranges

Open

#895 opened on Oct 6, 2022 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement field types support

Dominant language: Java
Stars: 176
Forks: 229
Avg merge: 2d 21h
Merged PRs (30d): 43

Description

Is your feature request related to a problem?

Some of OpenSearch data types are not supported. V2 just ignores columns with them.

Range types:
- integer_range
- long_range
- double_range
- float_range
- date_range
- ip_range
String
- token_count
Geographic
- `geo_shape

Other types (TBD how to interpret them):

alias
Object
- join
Autocomplete - interpret as strings TBD
- completion
- search_as_you_type
Rank - interpret as numbers/nested TBD
- rank_feature
- rank_features

What solution would you like?

SQL plugin should support querying on these types.

What alternatives have you considered?

First stage of implementation should support types from the first list above.
All these types could be processed as strings

Do you have any additional context?

#465
#891

Contributor guide

Open the contributing 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

No source file or test is named. Start by locating the SQL plugin's handling of OpenSearch field types and review the context in #465 and #891. Done means SQL queries support the six range types, token_count, and geo_shape; the remaining types need an agreed interpretation.

Written by the indexing model from the issue text.

Assessment

Tech stack: java, sql
Domain: backend, databases
Issue type: Feature
Difficulty: 4/5
Estimated time: 3-5 days
Activity status: Stale
Clarity: Mostly clear
Newbie friendliness: 45/100

A short digest of beginner-friendly GitHub issues.