[
https://issues.apache.org/jira/browse/IGNITE-4108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15837692#comment-15837692
]
Andrew Mashenkov commented on IGNITE-4108:
------------------------------------------
[~vozerov],
actually, impact is perceptible if user have many functions that we want to use
in number of caches. E.g. migration of old application with many stored
procedures to ignite.
Unfortunatelly, H2 does not support global functions and we need to add them to
every schema.
The best solution is to add global functions support. If it impossible, it
would be nice to have a workaround here.
For now, I do not see a way how global functions can be added.
> 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
> Priority: Minor
> Labels: performance
>
> SQL functions aliases need to be created for each schema. Their creation runs
> during cache initialization, but implemented in sequential manner.
> It would be great to have a global functions support. Otherwise, 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)
