[
https://issues.apache.org/jira/browse/PIG-4160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14190819#comment-14190819
]
Thejas M Nair commented on PIG-4160:
------------------------------------
I think it would be useful to retain mention of the old additional.jars
parameter in the web docs, Saying that it is similar to .jars.comma but
separated by the OS path charactor and does not allow for scheme to be
specified (and that the use of jars.comma is preferred)
> -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, PIG-4160-3.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)
