You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/11/03 16:44:59 UTC
[jira] [Commented] (DRILL-4995) Allow lazy init when dynamic UDF
support is disabled
[ https://issues.apache.org/jira/browse/DRILL-4995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15633392#comment-15633392 ]
ASF GitHub Bot commented on DRILL-4995:
---------------------------------------
GitHub user arina-ielchiieva opened a pull request:
https://github.com/apache/drill/pull/645
DRILL-4995: Allow lazy init when dynamic UDF support is disabled
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/arina-ielchiieva/drill DRILL-4995
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/drill/pull/645.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #645
----
commit b0b7446697c8b64004f194dd0c1b2ed2fdd23e79
Author: Arina Ielchiieva <ar...@gmail.com>
Date: 2016-11-03T16:20:04Z
DRILL-4995: Allow lazy init when dynamic UDF support is disabled
----
> Allow lazy init when dynamic UDF support is disabled
> ----------------------------------------------------
>
> Key: DRILL-4995
> URL: https://issues.apache.org/jira/browse/DRILL-4995
> Project: Apache Drill
> Issue Type: Bug
> Components: Functions - Drill
> Affects Versions: 1.9.0
> Reporter: Roman
> Assignee: Arina Ielchiieva
> Fix For: 1.9.0
>
>
> Steps in 2 nodes cluster:
> In 1st node:
> 1. Register jar
> 2. Run function (success)
> 3. Disable dynamic UDF support
> 4. Run function again (success)
> In 2nd node:
> 5. Try to run function (failed).
> In 1st node the function was initialized before disabling dynamic UDF support. But in 2nd node the function was not initialized. So It seems we need to allow lazy initialization when dynamic UDF support is disabled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)