[
https://issues.apache.org/jira/browse/PIG-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Dai resolved PIG-1566.
-----------------------------
Resolution: Fixed
Release Note:
User can use globbing in register statement. Pig will search for matching jars
in local file system (either relative path or absolute path). eg:
register /homes/user/pig/*.jar
register *.jar
register jars/*.jar
Relative path is relative to user's working directory.
Globbing does not support remote file system such as hdfs, s3 (register without
globbing do).
The behavior for register without globbing remains the same.
Hadoop Flags: [Reviewed]
Patch committed to trunk.
> Support globbing for registering jars in pig script.
> ----------------------------------------------------
>
> Key: PIG-1566
> URL: https://issues.apache.org/jira/browse/PIG-1566
> Project: Pig
> Issue Type: Improvement
> Affects Versions: 0.7.0
> Reporter: Ravi Phulari
> Assignee: Daniel Dai
> Fix For: 0.9.0
>
> Attachments: PIG-1566-2.patch, PIG_1566_0.patch, PIG_1566_1.patch
>
>
> Currently user can not register pig jars with globing.
> For example following register script will fail.
> {quote}
> register /etc/jars/*.jar
> {quote}
> It will be great if we can support such globing for registering jars.
> Release notes:
> We allow globbing in register statement. User can use "*" to denote a
> globbing, eg:
> register key*.jar
> register /home/jarpath/key*.jar
> register jars/key*.jar
> The path can be absolute path or relative path start with working directory.
> Note globbing does not further search in classpath as non-globbing case does,
> eg:
> "register key1234.jar" works if key1234.jar in classpath, but not in working
> directory, however,
> "register key*.jar" will not locate key1234.jar in this case.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
