You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Raghu Angadi (JIRA)" <ji...@apache.org> on 2012/07/17 00:58:35 UTC
[jira] [Created] (PIG-2819) ObjectSerializer should support
classloader
Raghu Angadi created PIG-2819:
---------------------------------
Summary: ObjectSerializer should support classloader
Key: PIG-2819
URL: https://issues.apache.org/jira/browse/PIG-2819
Project: Pig
Issue Type: Improvement
Components: impl
Reporter: Raghu Angadi
{ObjectSerializer} is pretty useful and could be used by UDF and other user code.
Currently its limitation is that the class that is being deserialized should be visible to root class loader (ie. should be part of CLASSPATH on the front end). The registered jars are not visibile. This is because {{java.io.ObjectInputStream}} used to deserialize is from the root classloader.
ObjectSerializer should support another method {{deserialize(str, ClassLoader)}}.
--
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-2819) ObjectSerializer should support
classloader
Posted by "Aniket Mokashi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443632#comment-13443632 ]
Aniket Mokashi commented on PIG-2819:
-------------------------------------
I discussed this briefly with Julien during the hackathon. This is useful for HCatLoader(ish) use case-(deserializing InputJobInfo). Do you guys have a patch for this?
> ObjectSerializer should support classloader
> -------------------------------------------
>
> Key: PIG-2819
> URL: https://issues.apache.org/jira/browse/PIG-2819
> Project: Pig
> Issue Type: Improvement
> Components: impl
> Reporter: Raghu Angadi
>
> {ObjectSerializer} is pretty useful and could be used by UDF and other user code.
> Currently its limitation is that the class that is being deserialized should be visible to root class loader (ie. should be part of CLASSPATH on the front end). The registered jars are not visibile. This is because {{java.io.ObjectInputStream}} used to deserialize is from the root classloader.
> ObjectSerializer should support another method {{deserialize(str, ClassLoader)}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira