You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Arina Ielchiieva (JIRA)" <ji...@apache.org> on 2016/11/28 11:15:58 UTC

[jira] [Commented] (DRILL-5044) After the dynamic registration of multiple jars simultaneously not all UDFs were registered

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

Arina Ielchiieva commented on DRILL-5044:
-----------------------------------------

The reason of this failure is that when update to remote UDFs registry failed with VersionMismatchException, retry logic was applied. Even though after retry, update was successful, jars were removed from remote UDFs area in finally block.

> After the dynamic registration of multiple jars simultaneously not all UDFs were registered
> -------------------------------------------------------------------------------------------
>
>                 Key: DRILL-5044
>                 URL: https://issues.apache.org/jira/browse/DRILL-5044
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Functions - Drill
>    Affects Versions: 1.9.0
>            Reporter: Roman
>            Assignee: Arina Ielchiieva
>
> I tried to register 21 jars simultaneously (property 'udf.retry-attempts' = 30) and not all jars were registered. As I see in output, all function were registered and /staging directory was empty, but not all of jars were moved into /registry directory. 
> For example, after simultaneously registration I saw "The following UDFs in jar test-1.1.jar have been registered: [test1(VARCHAR-REQUIRED)" message, but this jar was not in /registry directory. When I tried to run function test1, I got this error: "Error: SYSTEM ERROR: SqlValidatorException: No match found for function signature test1(<CHARACTER>)". And when I tried to reregister this jar, I got "Jar with test-1.1.jar name has been already registered".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)