[
https://issues.apache.org/jira/browse/BEAM-10607?focusedWorklogId=471013&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-471013
]
ASF GitHub Bot logged work on BEAM-10607:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 15/Aug/20 05:26
Start Date: 15/Aug/20 05:26
Worklog Time Spent: 10m
Work Description: robertwb commented on a change in pull request #12493:
URL: https://github.com/apache/beam/pull/12493#discussion_r470940566
##########
File path:
sdks/java/extensions/sql/src/main/java/org/apache/beam/sdk/extensions/sql/impl/rel/BeamTableFunctionScanRel.java
##########
@@ -232,7 +233,11 @@ private Schema getKeySchema(Schema inputSchema,
List<Integer> keys) {
upstream
.apply(
"assignEventTimestamp",
- WithTimestamps.<Row>of(row ->
row.getDateTime(windowFieldIndex).toInstant())
+ WithTimestamps.<Row>of(
+ row ->
+ Instant.ofEpochMilli(
Review comment:
I think there'll be surprising loss of precision if this field is used
for windowing (say, with TimestampCombiner.EARLIEST) and then the timestamp is
inspected (is even available from SQL, right?) and has been truncated. (Or any
other conversion from Row to Beam and back again being lossy.)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 471013)
Time Spent: 1h (was: 50m)
> Support micro-second ZetaSQL TIMESTAMP in BeamSQL
> -------------------------------------------------
>
> Key: BEAM-10607
> URL: https://issues.apache.org/jira/browse/BEAM-10607
> Project: Beam
> Issue Type: New Feature
> Components: dsl-sql-zetasql
> Reporter: Robin Qiu
> Assignee: Zijie Song
> Priority: P2
> Time Spent: 1h
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
