[
https://issues.apache.org/jira/browse/PIG-4011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14030005#comment-14030005
]
Rohini Palaniswamy commented on PIG-4011:
-----------------------------------------
Any idea why PigContext differs in each jar?
> Pig should not put PigContext in job.jar to help jar dedup
> ----------------------------------------------------------
>
> Key: PIG-4011
> URL: https://issues.apache.org/jira/browse/PIG-4011
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.13.0
> Reporter: Aniket Mokashi
> Fix For: 0.14.0
>
>
> Job jars are largely identical from job to job (just the pig classes and
> their dependencies). However, there is pigContext in the job jar, and that
> seems to change from job to job.As a result, the job jars are basically
> uncacheable in the shared cache. It would be great if we can find a way to
> separate the pig context and store it in the distributed cache separate from
> the (stable) job jar. That would give us a better chance to store the job jar.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
