[
https://issues.apache.org/jira/browse/PIG-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13056889#comment-13056889
]
Raghu Angadi commented on PIG-1566:
-----------------------------------
Filed PIG-2142 as follow up.. the patch brings the implementation closer to PIG
0.8.
This patch here has some change that are not described :
- it tries to resolve the relative paths.
- if glob or resource matches more than one file, it returns none (must be a
typo). This should be a blocker or we should update the release notes?
> 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
