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 2017/01/25 12:46:26 UTC

[jira] [Updated] (IGNITE-4108) SQL: optimize sql functions aliases creation

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

Andrew Mashenkov updated IGNITE-4108:
-------------------------------------
    Description: 
SQL functions aliases need to be created for each schema. Their creation runs during cache initialization, but implemented in sequential manner. 

We can make it in parallel or create bulk query or make in background to reduce cache start time.

Startpoint is org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.createSqlFunctions() method




  was:
SQL functions aliases need to be created for each schema. Their creation runs during cache initialization, but implemented in sequential manner. 

We can make it in parallel to reduce cache start time.

Startpoint is org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.createSqlFunctions() method





> SQL: optimize sql functions aliases creation
> --------------------------------------------
>
>                 Key: IGNITE-4108
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4108
>             Project: Ignite
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 1.6, 1.7
>            Reporter: Andrew Mashenkov
>              Labels: performance
>
> SQL functions aliases need to be created for each schema. Their creation runs during cache initialization, but implemented in sequential manner. 
> We can make it in parallel or create bulk query or make in background to reduce cache start time.
> Startpoint is org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.createSqlFunctions() method



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