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

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ASTERIXDB-1980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16082546#comment-16082546 ] 

ASF subversion and git services commented on ASTERIXDB-1980:
------------------------------------------------------------

Commit e762ddfd872e0b2e95079f42c5cee846caeba4ae in asterixdb's branch refs/heads/master from [~dlychagin-cb]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=e762ddfd ]

[ASTERIXDB-1980][FUNC] Cleanup FunctionManager lifecycle

- user model changes: no
- storage format changes: no
- interface changes: yes

Details:
- Moved FunctionCollection
  from asterix-algebra/org.apache.asterix.translator.util
  to   asterix-runtime/org.apache.asterix.runtime.functions
- Moved FunctionManagerHolder
  from asterix-om/org.apache.asterix.om.functions
  to   asterix-runtime/org.apache.asterix.runtime.functions
- Removed IDataFormat.registerRuntimeFunctions()

Change-Id: If96e425a096bc0312a68d81b04686d7165f1a1fd
Reviewed-on: https://asterix-gerrit.ics.uci.edu/1873
Sonar-Qube: Jenkins <je...@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <je...@fulliautomatix.ics.uci.edu>
BAD: Jenkins <je...@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <je...@fulliautomatix.ics.uci.edu>
Reviewed-by: Yingyi Bu <bu...@gmail.com>


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