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

Posted to notifications@asterixdb.apache.org by "Dmitry Lychagin (JIRA)" <ji...@apache.org> on 2017/07/11 17:17:00 UTC

[jira] [Resolved] (ASTERIXDB-1980) Cleanup FunctionManager lifecycle

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

Dmitry Lychagin resolved ASTERIXDB-1980.
----------------------------------------
    Resolution: Fixed

> Cleanup FunctionManager lifecycle
> ---------------------------------
>
>                 Key: ASTERIXDB-1980
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1980
>             Project: Apache AsterixDB
>          Issue Type: Improvement
>            Reporter: Dmitry Lychagin
>            Assignee: Dmitry Lychagin
>            Priority: Minor
>
> Currently FunctionManager is initialized from APIFramework's static block by calling FormatUtils.getDefaultFormat().registerRuntimeFunctions(). APIFramework is initialized by QueryTranslator and therefore FunctionManager is only populated after a query or DDLs is processed by the system. This is suboptimal because other parts of the system might also need to obtain function implementations from the FunctionManager (e.g. jobs submitted during rebalancing). 
> We should make sure that FunctionManager is always populated with built-in functions.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)