Well, you don't do it with props.conf. DBX 3.x uses HEC to talk to itself, and in that conversation the timezone gets baked in, so that props.conf settings won't matter.
timezone = <time zone identifier> # optional, default uses JVM time zone # The identifier could be: # an offset from UTC/Greenwich, that uses the same offset regardless given date-time e.g. +08:00 # an area where a specific set of rules for finding the offset from UTC/Greenwich apply e.g. Europe/Paris.
So, it has to be set for the whole connection. So if you have a connection that has different tables with timestamps in different timezones, you will have to get creative.
@dshpritz What if the database is running in UTC time and I need it to report in live time to me ( instead of writing only when that UTC time hits ), would i change the localTimezoneConversion line item to True to convert to the time listed in the Timezone?.
Database is running in UTC time ( 4 hours ahead of me )
I have in my config the timezone being Eastern.
If i enable localtimezoneconversation - will it adjust the time to index to eastern instead of UTC?