[
https://issues.apache.org/jira/browse/AVRO-3476?focusedWorklogId=752607&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-752607
]
ASF GitHub Bot logged work on AVRO-3476:
----------------------------------------
Author: ASF GitHub Bot
Created on: 05/Apr/22 01:41
Start Date: 05/Apr/22 01:41
Worklog Time Spent: 10m
Work Description: zcsizmadia commented on PR #1634:
URL: https://github.com/apache/avro/pull/1634#issuecomment-1088185282
@kojiromike I had similar concerns about the absolutness of the long value
when I did #1628. Some unit tests would be great to specify the the from /to
long conversion between a long and an absolute time (utc) maybe if there is
any. If there is none, I am not sure how 2 language implementation can be
determinstic in serialization and deserelization.
Issue Time Tracking
-------------------
Worklog Id: (was: 752607)
Time Spent: 0.5h (was: 20m)
> Python implementation does not support local-timestamp-micros and
> local-timestamp-millis
> ----------------------------------------------------------------------------------------
>
> Key: AVRO-3476
> URL: https://issues.apache.org/jira/browse/AVRO-3476
> Project: Apache Avro
> Issue Type: Bug
> Components: python
> Affects Versions: 1.11.0
> Reporter: Eric
> Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Even though [they are present in the
> spec|https://avro.apache.org/docs/1.11.0/spec.html#Local+timestamp+(millisecond+precision)],
> the Python implementation does not support logical types
> local-timestamp-micros and local-timestamp-millis.
> When trying to use them, you get the following:
> {code:python}
> .../lib/python3.8/site-packages/avro/schema.py:1048: IgnoredLogicalType:
> Unknown local-timestamp-micros, using long.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
