Mailing-List: contact dev-help@pig.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@pig.apache.org
Date: Wed, 23 Nov 2011 06:45:40 +0000 (UTC)
From: "Dmitriy V. Ryaboy (Updated) (JIRA)" <jira@apache.org>
To: pig-dev@hadoop.apache.org
Message-ID: 
 <1518133950.5321.1322030740101.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1898073339.5314.1322030560130.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (PIG-2384) Generic Invokers should use PigContext
 to resolve classes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Dmitriy V. Ryaboy updated PIG-2384:
-----------------------------------

    Attachment: PIG-2384.patch

Attaching patch that reportedly fixes the issue.

It's fairly trivial, and I don't think the cost of setting up the multiple-classloaders test case is worth the time.. will commit in a few days if no objections are raised.
                
> Generic Invokers should use PigContext to resolve classes
> ---------------------------------------------------------
>
>                 Key: PIG-2384
>                 URL: https://issues.apache.org/jira/browse/PIG-2384
>             Project: Pig
>          Issue Type: Bug
>            Reporter: Dmitriy V. Ryaboy
>            Assignee: Dmitriy V. Ryaboy
>         Attachments: PIG-2384.patch
>
>
> Some users report having to put their jars on Pig's classpath in addition to "register"ing them in order to get Generic Invokers to pick up their classes. This is due to us using Class.forName instead of relying on PigContext's resolveClassName (which handles all the dynamically registered classes).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira