[
https://issues.apache.org/jira/browse/IGNITE-7363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16318605#comment-16318605
]
Ilya Kasnacheev commented on IGNITE-7363:
-----------------------------------------
It probably has to do with H2 type conversions, especially DateTimeUtils.
> Inconsistent millis in java.util.Date when retrieved in SELECT query
> --------------------------------------------------------------------
>
> Key: IGNITE-7363
> URL: https://issues.apache.org/jira/browse/IGNITE-7363
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Affects Versions: 2.3
> Reporter: Ilya Kasnacheev
> Attachments: 19222.zip
>
>
> ~ when querying for java.util.Date field in SELECT query it returns a
> java.sql.Timestamp, and when getTime() on that Timestamp is called it returns
> different milliseconds value than in original java.util.Date, in case Time
> Zone is different on client and on server. Using get() the correct
> java.util.Date is obtained. Please see reproducer, kudos
> http://apache-ignite-users.70518.x6.nabble.com/Date-type-field-in-select-query-is-returning-wrong-value-when-Time-zones-of-Ignite-Client-and-Servert-tc19222.html
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
