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
I'm currently working on a private change to integrate an ORC writer into Velox. During some initial tests, I noticed that the existing ColumnReader under DWRF has the EPOCH_OFFSET hardcoded to PST, as seen in IntCodecCommon.
Could someone explain the reasoning behind this choice? This is causing some challenges, especially since in ORC, when using TIMESTAMP_INSTANT, the default timezone is UTC. (I understand that Timestamp_instant is not yet enabled in Velox.)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello everyone,
I'm currently working on a private change to integrate an ORC writer into Velox. During some initial tests, I noticed that the existing ColumnReader under DWRF has the EPOCH_OFFSET hardcoded to PST, as seen in IntCodecCommon.
Could someone explain the reasoning behind this choice? This is causing some challenges, especially since in ORC, when using TIMESTAMP_INSTANT, the default timezone is UTC. (I understand that Timestamp_instant is not yet enabled in Velox.)
Beta Was this translation helpful? Give feedback.
All reactions