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?
OpenSearch timestamp type is different from other databases including Calcite.
In Calcite, timestamp is calculated as long while don't support nanos precision.
In OpenSearch, timestamp is calculated as string and support nanos precision. In V2, we support comparison between string and columns of timestamp type, and timestamp related functions also support pass in string as its arguments.
What solution would you like?
Convert opensearch timestamp as UDT instead of calcite's timestamp
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:
Is your feature request related to a problem?
OpenSearch timestamp type is different from other databases including Calcite.
In Calcite, timestamp is calculated as long while don't support nanos precision.
In OpenSearch, timestamp is calculated as string and support nanos precision. In V2, we support comparison between string and columns of timestamp type, and timestamp related functions also support pass in string as its arguments.
What solution would you like?
Convert opensearch timestamp as UDT instead of calcite's timestamp
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: