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
Copy file name to clipboardexpand all lines: velox/docs/develop/timestamp.rst
+18-18
Original file line number
Diff line number
Diff line change
@@ -73,9 +73,9 @@ used to efficiently represent timezones, preventing the use of inefficient
73
73
timezone string names like ``America/Los_Angeles``. Considering there are about
74
74
2k valid timezone definitions, 12 bits are enough to represent timezone IDs.
75
75
76
-
Timezone IDs in Velox are based on the id map used by Presto and are
77
-
`available here <https://github.com/prestodb/presto/blob/master/presto-common/src/main/resources/com/facebook/presto/common/type/zone-index.properties>`_.
78
-
They are automatically generated using `this script <https://github.com/facebookincubator/velox/blob/main/velox/type/tz/gen_timezone_database.py>`_.
76
+
Timezone IDs in Velox are based on the id map used by Presto and are
77
+
`available here <https://github.com/prestodb/presto/blob/master/presto-common/src/main/resources/com/facebook/presto/common/type/zone-index.properties>`_.
78
+
They are automatically generated using `this script <https://github.com/facebookincubator/velox/blob/main/velox/type/tz/gen_timezone_database.py>`_.
79
79
While timezone IDs are an implementation detail and ideally should not leak
80
80
outside of Velox execution, they are exposed if data containing
81
81
TimestampWithTimezones are serialized, for example.
@@ -98,7 +98,7 @@ ID).
98
98
99
99
However, unpacking/converting a TimestampWithTimezone into an absolute time
0 commit comments