opwvhk commented on PR #2554: URL: https://github.com/apache/avro/pull/2554#issuecomment-1773717601
> Does anyone know what is the idea behind having both `local-timestamp-**` and `timestamp-**` if the timezone is not encoded with the integer ? Since the application should deal with the timezone then why do we need two types ? Sometimes, especially with legacy systems, the timezone is 'understood'. Usually because originally there was only one timezone (of the country the company operated in). This starts to break down of course when you go to an international setting, but rewriting is terribly expensive and often outside of any budget. In such situations I may chose the local time(stamp) types as a warning signal. -- 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]
