ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Mashenkov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-4031) SQL: Optimize Date\Time\Timestamp function arguments conversion.
Date Wed, 05 Oct 2016 11:14:20 GMT

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

Andrew Mashenkov updated IGNITE-4031:
-------------------------------------
    Summary: SQL: Optimize Date\Time\Timestamp function arguments conversion.  (was: SQL:
Optimize Date\Time\Timestamp function arguments convertion.)

> SQL: Optimize Date\Time\Timestamp function arguments conversion.
> ----------------------------------------------------------------
>
>                 Key: IGNITE-4031
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4031
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: SQL
>    Affects Versions: 1.6, 1.7
>            Reporter: Andrew Mashenkov
>              Labels: performance, sql
>
> When sql function with Date\Time\Timestamp arguments is used, H2 internals convert these
objects using java.util.Calendar before pass them as arguments.
> In current H2 version we use: DateTimeUtils holds cache java.util.Calendar instance in
static field and synchronize every operation on it.
> If its possible, we need to have workaround to use java.util.Calendar more effectively
as it done for timestamp fields. See IgniteH2Indexing.wrap() method.



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

Mime
View raw message