GridGain Community Edition

Hi,

I'm using pyignite to query ignite for my application. I use the jdbc driver to view data on the UI.

There's  a timestamp field in my table structure which does not return the same timestamp with pyignite vs when I query with JDBC driver[dBeaver UI].
I'm assuming this is because of the timezone difference.

I have deployed ignite with docker on alpine.

I want to understand how ignite handles timestamps and how I can achieve consistency or make my code timezone aware.

Thanks

------------------------------
Saurabh Wahile
Data Science Engineer
Lok Suvidha Finance
------------------------------

Hello Saurabh.
It looks like pyignite or DBeaver uses old jdbc driver (from 2.7.* ignite). 
The modern driver uses the cluster timezone, while the old one casts the timestamp to the local timezone. 




------------------------------
Ilya Kazakov
Software Engineer
Grid Gain
------------------------------

Original Message:
Sent: 11-15-2020 10:03 AM
From: Saurabh Wahile
Subject: Timestamp irregularities with pyigntite vs jdbc driver

Hi,

I'm using pyignite to query ignite for my application. I use the jdbc driver to view data on the UI.

There's  a timestamp field in my table structure which does not return the same timestamp with pyignite vs when I query with JDBC driver[dBeaver UI].
I'm assuming this is because of the timezone difference.

I have deployed ignite with docker on alpine.

I want to understand how ignite handles timestamps and how I can achieve consistency or make my code timezone aware.

Thanks

------------------------------
Saurabh Wahile
Data Science Engineer
Lok Suvidha Finance
------------------------------

Please clarify in what case you get a date different from the recorded date: in pyingite or in DBeaver? If in DBeaver, then you can try to change the jdbc driver to the driver from your GridGain installation.

------------------------------
Ilya Kazakov
Software Engineer
Grid Gain
------------------------------

Original Message:
Sent: 11-15-2020 10:03 AM
From: Saurabh Wahile
Subject: Timestamp irregularities with pyigntite vs jdbc driver

Hi,

I'm using pyignite to query ignite for my application. I use the jdbc driver to view data on the UI.

There's  a timestamp field in my table structure which does not return the same timestamp with pyignite vs when I query with JDBC driver[dBeaver UI].
I'm assuming this is because of the timezone difference.

I have deployed ignite with docker on alpine.

I want to understand how ignite handles timestamps and how I can achieve consistency or make my code timezone aware.

Thanks

------------------------------
Saurabh Wahile
Data Science Engineer
Lok Suvidha Finance
------------------------------