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 2018/03/16 14:51:00 UTC
[jira] [Updated] (IGNITE-4031) SQL: Optimize Date\Time\Timestamp
function arguments conversion.
[ https://issues.apache.org/jira/browse/IGNITE-4031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov updated IGNITE-4031:
------------------------------------
Labels: sql-performance (was: performance)
> SQL: Optimize Date\Time\Timestamp function arguments conversion.
> ----------------------------------------------------------------
>
> Key: IGNITE-4031
> URL: https://issues.apache.org/jira/browse/IGNITE-4031
> Project: Ignite
> Issue Type: Task
> Components: sql
> Affects Versions: 1.6
> Reporter: Andrew Mashenkov
> Priority: Major
> Labels: sql-performance
>
> 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.
> Startpoint: GridSQLQueryParser.FUNC_ALIAS
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)