Hi Chris,
> By the way ... why not use the default Timezone configured for the VM
running the client code?
I don't even think there is a need to manually configure this at all.
You are right, and it's designed as you said right now.* If the timezone is
not set explicitly, the default timezone of
Hi all,
great discussion ... I guess the first bug reports you got from me when working
on the initial maven build were related to this :-)
By the way ... why not use the default Timezone configured for the VM running
the client code?
I don't even think there is a need to manually configure
Hi,
very good addition, indeed.
As one of the first users "far away" from China it was always a bit of math for
me to get everything together with default settings (UTC+8?) : )
Julian
Am 30.10.20, 02:59 schrieb "Xiangwei Wei" :
In the previous design, the timezone was set in IoTDB server
In the previous design, the timezone was set in IoTDB server configuration.
When one client gets the connection from the server,* it will keep the same
timezone as server.*
However, since IoTDB is becoming more and more international. Some user may
encounter problems, as their clients are in
