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.

Sign up for GitHub

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

Jump to bottom

[FEATURE] Support more opensearch data types, like ranges #895

Open

Yury-Fridlyand opened this issue Oct 6, 2022 · 1 comment

Labels

Collaborator

Yury-Fridlyand commented Oct 6, 2022 •

edited

Loading

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?

The text was updated successfully, but these errors were encountered:

Yury-Fridlyand added enhancement untriaged labels

dai-chen removed the untriaged label

Collaborator

dai-chen commented Oct 10, 2022

Old tracking issue for reference: #44

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment