[
https://issues.apache.org/jira/browse/PIG-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Dai updated PIG-4160:
----------------------------
Attachment: PIG-4160-2.patch
Thinking that again, I feel we might need to deal with mixed jar origin in one
job, eg, some jars are in hdfs and some jars are local. We shall allow the full
scheme so user can specify if the jar is local or hdfs. However,
pig.additional.jars is colon separated and make it impossible. I'd like to
introduce a comma separated equivalent to make the things flow. Attach patch.
> -forcelocaljars / -j flag when using a remote url for a script
> --------------------------------------------------------------
>
> Key: PIG-4160
> URL: https://issues.apache.org/jira/browse/PIG-4160
> Project: Pig
> Issue Type: Improvement
> Components: impl
> Affects Versions: 0.14.0
> Reporter: Andrew C. Oliver
> Labels: patch
> Fix For: 0.14.0
>
> Attachments: PIG-4160-2.patch, forcelocal.trunk.patch,
> forcelocal.withtests.patch
>
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> patch adds a -j/forcelocaljars flag which if enabled allows you to do
> pig -j -useHCatalog hdfs://myserver:8020/load/scripts/mydir/myscript.pig
> thus loading the pig script REMOTELY
> while loading the jar files LOCALLY
> One does this to avoid a single point of failure but avoid one central
> interversion dependent repository for all the jars across all teams/projects.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
