[
https://issues.apache.org/jira/browse/IGNITE-4172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16110663#comment-16110663
]
Alexandr Fedotov edited comment on IGNITE-4172 at 8/2/17 10:14 AM:
-------------------------------------------------------------------
Apart from the improvements introduced by
[IGNITE-5483|https://issues.apache.org/jira/browse/IGNITE-5483] the following
should be addressed:
1. {{java.time.LocalTime}}, {{java.time.LocalDate}},
{{java.time.LocalDateTime}} are not supported as cache values or keys.
2. LocalDateTime is stored as Timestamp, which should be accounted when
applying a custom SQL functions. Probably that's a tradeoff for the moment.
was (Author: asfedotov):
Apart from the improvements introduced by
[IGNITE-5483|https://issues.apache.org/jira/browse/IGNITE-5483] the following
should be addressed:
1. {{java.time.LocalTime}}, {{java.time.LocalDate}},
{{java.time.LocalDateTime}} are not supported as cache values or keys.
2. LocalDateTime is stored as Timestamp, which should be accounted when
applying a custom SQL functions.
> SQL: Add support for Java 8 Time API classes in date\time functions
> -------------------------------------------------------------------
>
> Key: IGNITE-4172
> URL: https://issues.apache.org/jira/browse/IGNITE-4172
> Project: Ignite
> Issue Type: Bug
> Reporter: Andrew Mashenkov
> Assignee: Alexandr Fedotov
> Fix For: 2.2
>
>
> We have is issue with querying LocalDateTime objects with our SQL engine.
> Next query can fails with error, if one of row localDateTimeField value has
> zero-time:
> select DATEDIFF('DAY', localDateTimeField, CURRENT_DATE ()) from t;
> Startpoint is IgniteH2Indexing.wrap() method.
> We need add support to these classes: LocalDate, LocalTime, LocalDateTime.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
