[
https://issues.apache.org/jira/browse/PIG-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12584559#action_12584559
]
Pi Song commented on PIG-112:
-----------------------------
Craig,
I like this concept. I have the same problem when I have to retype long package
names everytime I refer to UDFs.
Comments :-
1. This "include" should be specific to each instance of PigContext so
packageImportList should be modified to non-static
2. Your example makes use of the token "include" but your code uses "import". I
prefer import but I also want to know other people's opinions.
3. I don't understand either why it affects only dump command. Can you
regenerate the patch using the latest trunk so that I can help you on this?
> 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.
