hadoop-pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Milind Bhandarkar (JIRA)" <j...@apache.org>
Subject [jira] Commented: (PIG-832) Make import list configurable
Date Thu, 18 Jun 2009 18:54:07 GMT

    [ https://issues.apache.org/jira/browse/PIG-832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721413#action_12721413
] 

Milind Bhandarkar commented on PIG-832:
---------------------------------------

Instead of a list, if you make it a map (i.e. short name -> fully qualified class name),
it will be much easier, as it will guarantee that each name has exactly one udf class associated
with it. It will also allow users to use udfs that have class names which are pig reserved
words. For example, If I have an existing UDF with a class name such as load or store, I can
still use them with a different name like myload, without having to rename the class.

So, I suggest:

{code}
java -jar pig.jar -Dimport.list+=MyLoad:com.xxxx.Load,Flatten:com.xxxx.Flatten,... 
{code}

If I do not specify -Dimport.list on the pig command line, then the default import.list is
used.

Thoughts ?

> Make import list configurable
> -----------------------------
>
>                 Key: PIG-832
>                 URL: https://issues.apache.org/jira/browse/PIG-832
>             Project: Pig
>          Issue Type: Improvement
>    Affects Versions: 0.2.0
>            Reporter: Olga Natkovich
>            Assignee: Daniel Dai
>             Fix For: 0.3.0
>
>
> Currently, it is hardwired in PigContext.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message