[
https://issues.apache.org/jira/browse/BEAM-12544?focusedWorklogId=623661&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-623661
]
ASF GitHub Bot logged work on BEAM-12544:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 16/Jul/21 15:03
Start Date: 16/Jul/21 15:03
Worklog Time Spent: 10m
Work Description: aromanenko-dev commented on pull request #15087:
URL: https://github.com/apache/beam/pull/15087#issuecomment-881515402
Well, in this case I'd say that we need to test it in the same way as we do
for `Avro(TimestampMillis)` but expecting milliseconds after two-sides
conversion which actually can be quite ambiguous from the user point
perspective (and that is why I'm asking if it's expected behaviour). Then in
this case we need to warn users about that in documentation as well (JavaDoc
and website).
Btw, are there any principal objections or difficulties to use a micros
representation for DATETIME field?
Afaik, @iemejia is OOO this week but he will be back soon and maybe can add
something on this.
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 623661)
Time Spent: 3h 40m (was: 3.5h)
> Add support for Avro timestamps in microseconds
> -----------------------------------------------
>
> Key: BEAM-12544
> URL: https://issues.apache.org/jira/browse/BEAM-12544
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-core
> Affects Versions: Not applicable
> Reporter: Tobias Hermann
> Priority: P2
> Fix For: Not applicable
>
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> GenericRecordToRowFn in AvroUtils does not support the logical Avro type
> "timestamp-micros". Instead of converting it to FieldType.DATETIME (as it
> does with "timestamp-millis") it just interprets it as a raw LONG.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
