You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2017/06/21 13:42:00 UTC

[jira] [Assigned] (IGNITE-5483) SqlQuery fails with WHERE clause on LocalDateTime field

     [ https://issues.apache.org/jira/browse/IGNITE-5483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladimir Ozerov reassigned IGNITE-5483:
---------------------------------------

    Assignee: Sergey Kalashnikov

> SqlQuery fails with WHERE clause on LocalDateTime field
> -------------------------------------------------------
>
>                 Key: IGNITE-5483
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5483
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>    Affects Versions: 2.0
>         Environment: Ignite 2.0.0
> Oracle JDK 1.8.0_121
>            Reporter: Benjamin Garaude
>            Assignee: Sergey Kalashnikov
>             Fix For: 2.1
>
>
> When performing a SqlQuery with a WHERE clause containing an {{=}} predicate on a field of type LocalDateTime, the query fails with  {{org.apache.ignite.IgniteCheckedException:Failed to execute SQL query.}} 
> This bug occurred in 2.0, the same SqlQuery was working fine on 1.9.
> If we dig into the details,the original exception is a {{ClassCastException}} on {{IgniteH2Indexing:3663}}.
> When doing the same kind of query with a WHERE clause on a String type, it works.
> You can find a test case showing that here: https://github.com/bgaraude/IgniteTest
> I think this is related to IGNITE-4172, but this ticket says that the patch has to be updated once H2 has been updated.
> It seems that ignite 2.0 uses an updated version of H2: 1.4.195. This H2 version supports LocalDateTime. At least {{org.h2.value.DataType.getTypeFromClass}} returns TimeStamp for the LocalDateTime class. But {{IgniteH2Indexing$RowDescriptor.wrap()}} has not been updated accordingly. Hence, the ClassCastException.
> Do you know a workaround i can use while this issue is fixed?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)