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 19:40:07 GMT

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

Milind Bhandarkar commented on PIG-832:

Hardwiring names that are not reserved words is likely to cause more pain in the long run.
What Daniel is proposing seems to be right for your assumptions 1, 2, and 3, though. But one
can easily think of several use cases where overriding on the command-line eases a lot of
pain. Assume that someone writes a new superfast PigStorage UDF, and wants to compare its
performance with the default PigStorage provided with Pig. Instead of modifying the entire
benchmark suite PigMix to use the new storage UDF, he/she can just make PigStorage point to
his own UDF on the commandline and run PigMix. It saves a lot of Pain.

> 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.

View raw message