[
https://issues.apache.org/jira/browse/PIG-4417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14318426#comment-14318426
]
Niels Basjes commented on PIG-4417:
-----------------------------------
At first glance this seems like a nice feature. I do see some points that need
attention:
# Which repo? In Maven I can define a custom repo to download the stuff from.
# Dependencies? Often pulling in 1 single dependency really requires a stream
of dependencies to be downloaded. How do I know which others I need if I
specify just the URL?
# Cache? If I point towards a URL, when and how often does it get downloaded
and where does it get cached?
I approached essentially the same usecase in a different way in this
demonstration project: https://github.com/nielsbasjes/pig-demo-project
Essentially I simply use Maven (but you can do the same with Gradle and all the
others) to solve this dependency problem for me and I only focused on getting
the whole testing and packaging to work right. In this setup the {{REGISTER}}
command 'always' degrades to the very simple
{code}
REGISTER lib/*.jar;
{code}
> 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
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
