You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem?
Currently, OpenSearch PPL data type and Spark PPL data type are not aligned. For instance, opensearch-project/opensearch-spark#1057.
What solution would you like?
We proposed a breaking change in OpenSearch PPL Data Type.
OpenSearch PPL Data Type
Spark PPL Data Type
Unified PPL Data Type
byte
tinyint
tinyint
short
smallint
smallint
integer
int
int
long
bigint
bigint
It is breaking change, and release in OpenSearch 3.0, change includes
Integration Test
Documentation
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.
The text was updated successfully, but these errors were encountered:
@penghuo , do you mean in 3.0.0, the PPL data type won't include byte, short, integer and long. instead, they will upgrade to
byte -> tinyint
short -> smallint
integer -> int
long -> bigint
@penghuo , do you mean in 3.0.0, the PPL data type won't include byte, short, integer and long. instead, they will upgrade to
byte -> tinyint
short -> smallint
integer -> int
long -> bigint
Is your feature request related to a problem?
Currently, OpenSearch PPL data type and Spark PPL data type are not aligned. For instance, opensearch-project/opensearch-spark#1057.
What solution would you like?
We proposed a breaking change in OpenSearch PPL Data Type.
It is breaking change, and release in OpenSearch 3.0, change includes
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.
The text was updated successfully, but these errors were encountered: