[
https://issues.apache.org/jira/browse/PIG-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14378313#comment-14378313
]
Ratandeep Ratti commented on PIG-4417:
--------------------------------------
Some of the reasons I can think of for this feature
* Dependencies (udf jars) are much more declarative which this change, instead
of copy jar to gateway and register in pig script, all the user has to do is
add the ivy coordinates in his register command. This saves an annoying step.
Also if the udf has other dependencies the annoyance is compounded.
* Platforms like Oozie can greatly benefit from this. Instead of shipping a
large zip of pig udfs along with the pig-script, users could upload the minimal
zip, the Pig script could take care of downloading those dependencies from the
internal/external repository. Most commonly used udfs/jars will automatically
be cached (ivy cached) . Ivy will resolve these commonly used jars from the
local cache. Instead of say every user bundling up the udf jar in his/her zip.
* By having ivy coordinates for udf jars we know exactly what version of a udf
jar is being used in a Pig script.
> Pig's register command should support automatic fetching of jars from repo.
> ---------------------------------------------------------------------------
>
> Key: PIG-4417
> URL: https://issues.apache.org/jira/browse/PIG-4417
> Project: Pig
> Issue Type: Improvement
> Reporter: Akshay Rai
> Assignee: Akshay Rai
>
> Currently Pig's register command takes a local path to a dependency jar .
> This clutters the local file-system as users may forget to remove this jar
> later.
> It would be nice if Pig supported a Gradle like notation to download the jar
> from a repository.
> Ex: At the top of the Pig script a user could add
> register '<group>:<module>:<version>';
> It should be backward compatible and should support a local file path if so
> desired.
> RB: https://reviews.apache.org/r/31662/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
