You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Andrew Mashenkov (JIRA)" <ji...@apache.org> on 2016/10/05 11:09:20 UTC

[jira] [Issue Comment Deleted] (IGNITE-3959) SQL: Optimize Date\Time fields conversion.

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

Andrew Mashenkov updated IGNITE-3959:
-------------------------------------
    Comment: was deleted

(was: Also i've noticed, that when we use aggregate sql function with timestamps, H2 needs to unwrap ValueTimestamp objects using java.util.Calendar to pass them as arguments.)

> SQL: Optimize Date\Time fields conversion.
> ------------------------------------------
>
>                 Key: IGNITE-3959
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3959
>             Project: Ignite
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 1.6, 1.7
>            Reporter: Andrew Mashenkov
>              Labels: performance
>
> SqlFieldsQueries slowdown on date\time fields processing due to ineffective java.util.Calendar usage for date manipulation by H2 database.
> Good point to start is IgniteH2Indexing.wrap() method. Make optimization for types DATE and TIME as it already done for TIMESTAMP type.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)