[
https://issues.apache.org/jira/browse/PIG-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615858#action_12615858
]
Daniel Dai commented on PIG-112:
--------------------------------
Hi, Craig,
I checked the patch. The problem is that token definition PACKAGE is in front
of token definition IDENTIFIER (line 48 in patch). So every token will be
interpretted as PACKAGE whenever possible. Simply move it behind will solve the
problem. Other code looks good. Can you regenerate the patch?
Thanks
> Allow Java packages to be searched for functions.
> -------------------------------------------------
>
> Key: PIG-112
> URL: https://issues.apache.org/jira/browse/PIG-112
> Project: Pig
> Issue Type: Improvement
> Reporter: Craig Macdonald
> Priority: Minor
> Attachments: patch.import
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Motivation: Why should a user have to supply the fully qualified name to his
> user defined function, if all the functions he ever uses are in a pre-defined
> list of packages?
> Currently PigContext has a list of Java packages that are searched for
> functions. Currently the list consists of the following
> packages:
> * org.apache.pig.builtin.
> * org.apache.pig.impl.builtin.
> * com.yahoo.pig.yst.sds.ULT.
> Users should be able to add to this packagelist.
> Example in Grunt:
> {noformat}
> include com.pig.function.package.
> {noformat}
> This has connections to imports in Java classes, namespaces in XQuery, and
> the PATH env var in shell scripting.
> Should be trivial to implement, or could be a property.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
