You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Julien Le Dem (Resolved) (JIRA)" <ji...@apache.org> on 2011/11/02 22:03:33 UTC

[jira] [Resolved] (PIG-2318) Push extra jars to distributed cache and use the classloader enxtension mechanism in PigContext to load them on the backend

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

Julien Le Dem resolved PIG-2318.
--------------------------------

    Resolution: Won't Fix

I'm closing this as won't fix because using a different classloader on the backend has too many side effects. In particular HBaseLoader included in the pig jar but its dependencies not, or other subtle things. Instead I will update PIG-2010 using the distributed cache.
                
> Push extra jars to distributed cache and use the classloader enxtension mechanism in PigContext to load them on the backend
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: PIG-2318
>                 URL: https://issues.apache.org/jira/browse/PIG-2318
>             Project: Pig
>          Issue Type: Improvement
>          Components: impl
>            Reporter: Julien Le Dem
>            Assignee: Julien Le Dem
>         Attachments: PIG-2318.patch, PIG-2318_2.patch, PIG-2318_3.patch, PIG-2318_4.patch
>
>
> This is related to PIG-2010 with a slightly different approach
> https://issues.apache.org/jira/browse/PIG-2010
> Currently Pig bundles up all dependencies in a single jar which is a lot of overhead when there are a lot of dependencies and short lived jobs. This patch instead pushes the dependencies to distributed cache and uses the PigContext classloading mechanism to make the UDFs available.
> Possible improvements: push jars to HDFS/distributed cache only once per script. have a cache on HDFS to avoid repeatedly pushing jars to HDFS.

--
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