asterixdb-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Lychagin (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (ASTERIXDB-1980) Cleanup FunctionManager lifecycle
Date Tue, 11 Jul 2017 17:17:00 GMT

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

Dmitry Lychagin closed ASTERIXDB-1980.
--------------------------------------

> 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)

Mime
View raw message