[GitHub] [pulsar] jerrypeng edited a comment on issue #4823: Support timezone information in Pulsar

[GitBox <gi...@apache.org>]

jerrypeng edited a comment on issue #4823: Support timezone information in Pulsar
URL: https://github.com/apache/pulsar/issues/4823#issuecomment-515309785
 
 
   I have a couple questions just to understand the rational behind having timezones with timestamp since I don't have extensive experience in how time should be represented in a database:
   
   1.  Since all unix timestamp are in UTC time does it make sense to have timezone information for publish_time especially since it is set by the system?  In presto, for a timestamp field, by default it displays the time in the local timezone anyways
   
   2. The user can set event_time, and from my understanding, users can offset the unix timestamp in UTC time by certain number of hours to correspond to a particular timezone.  Is this a best practice?  I am not an expert in how time should be represented in a database.  Just searching what other have said online:
   
   https://justatheory.com/2012/04/postgres-use-timestamptz/
   
   https://medium.com/@vivekmadurai/how-to-deal-with-date-and-time-across-time-zones-39b1bd747f35
   
   Should we set or assume every timestamp to be in UTC time for consistency sake? Presto will display a timestamp field in local time

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services