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
Each data format may support a different underlying type, so appropriate conversions need to be implemented. Currently, values are truncated to the precision expected by Presto. We should update to do rounding to match the type semantics.
There's a performance cliff above timestamp(6), so equating Hive's timestamp to Presto timestamp(9) might not be optimal. We'll probably want a configuration option in the connector to indicate how Hive timestamps should be mapped. We'll also need this for backward compatibility. If existing Hive tables all switch to timestamp(9), may queries may start to fail due to type mismatch issues.
The text was updated successfully, but these errors were encountered:
Considerations
timestamp(3)
. The metastore supports "timestamp with optional nanosecond precision" (see https://cwiki.apache.org/confluence/display/Hive/LanguageManual+Types#LanguageManualTypes-TimestampstimestampTimestamps).The text was updated successfully, but these errors were encountered: