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
{{ message }}
Repository navigation
Commit c4bb488
Browse filesBrowse the repository at this point in the historyBrowse files
fix(operator): parse the timestamp column at microsecond resolution
pandas parses into nanoseconds by default, which reach only 1677 to 2262, so
the exported script ended the run on a moment the executor reads like any
other: it holds a java.sql.Timestamp, where the year 2500 is ordinary.
Microseconds cover the whole range the executor answers for, and the fields
are compared against it at and past the nanosecond edge.
Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
Copy file name to clipboardExpand all lines: common/workflow-operator/src/main/scala/org/apache/texera/amber/operator/extractdatetime/ExtractDateTimeOpDesc.scala
+6-3Lines changed: 6 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -109,9 +109,12 @@ class ExtractDateTimeOpDesc extends MapOpDesc with StandaloneCodeGenerator {
Copy file name to clipboardExpand all lines: common/workflow-operator/src/test/scala/org/apache/texera/amber/operator/extractdatetime/ExtractDateTimeOpDescSpec.scala
0 commit comments