martin-g commented on PR #2554: URL: https://github.com/apache/avro/pull/2554#issuecomment-1774592187
The problem is that in the Avro data format there is no timezone data in both types. It is left to the application to provide it, e.g. by storing it in a sibling field. My question is: Do we need both types `timestamp-xyz` and `local-timestamp-xyz` ? It looks to me that it is up to the application logic to decide how to interpret the `long`/`i64` value. We are going to add one more pair of such types! I understand that it is impossible to remove an existing type from the spec (v1)! And adding a new type should be consistent with the old ones! So there is no much that can be done at the moment but to acknowledge the situation. The best would be the `timestamp-xyz` types to encode both the `long` and the timezone in one field. Then the Avro SDKs could provide help with deserializing it to language specific classes, e.g. `OffsetDateTime` in Java. -- 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]
