You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Dmitriy V. Ryaboy (Created) (JIRA)" <ji...@apache.org> on 2011/11/23 07:42:40 UTC
[jira] [Created] (PIG-2384) Generic Invokers should use PigContext
to resolve classes
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
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
[jira] [Closed] (PIG-2384) Generic Invokers should use PigContext
to resolve classes
Posted by "Dmitriy V. Ryaboy (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy V. Ryaboy closed PIG-2384.
----------------------------------
> 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
> Fix For: 0.10, 0.11
>
> 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
[jira] [Resolved] (PIG-2384) Generic Invokers should use PigContext
to resolve classes
Posted by "Dmitriy V. Ryaboy (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy V. Ryaboy resolved PIG-2384.
------------------------------------
Resolution: Fixed
Fix Version/s: 0.11
0.10
Committed to trunk and 0.10 branch
> 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
> Fix For: 0.10, 0.11
>
> 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
[jira] [Commented] (PIG-2384) Generic Invokers should use
PigContext to resolve classes
Posted by "Alan Gates (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-2384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13159454#comment-13159454 ]
Alan Gates commented on PIG-2384:
---------------------------------
+1, looks fine.
> 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
[jira] [Updated] (PIG-2384) Generic Invokers should use PigContext
to resolve classes
Posted by "Dmitriy V. Ryaboy (Updated) (JIRA)" <ji...@apache.org>.
[ 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