GridGain Community Edition

Back to discussions
Expand all | Collapse all

Timestamp irregularities with pyigntite vs jdbc driver

  • 1.  Timestamp irregularities with pyigntite vs jdbc driver

    Posted 11-15-2020 10:04 AM
    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
    ------------------------------


  • 2.  RE: Timestamp irregularities with pyigntite vs jdbc driver

    Posted 11-16-2020 07:14 PM
    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


  • 3.  RE: Timestamp irregularities with pyigntite vs jdbc driver

    Posted 11-17-2020 12:43 AM
    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