pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Coveney (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PIG-2692) Make the Pig unit faciliities more generalizable and update javadocs
Date Fri, 11 May 2012 00:33:50 GMT

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

Jonathan Coveney commented on PIG-2692:
---------------------------------------

Anyone who adds documentation to Pig will get a round on me, should we ever be in the same
bar
                
> Make the Pig unit faciliities more generalizable and update javadocs
> --------------------------------------------------------------------
>
>                 Key: PIG-2692
>                 URL: https://issues.apache.org/jira/browse/PIG-2692
>             Project: Pig
>          Issue Type: Improvement
>            Reporter: Jeremy Hanna
>            Priority: Minor
>
> This ticket has two goals for Pig unit:
> 1) Pig unit has a really nice method assertOutput(String inputAlias, String[] inputValues,
String outputAlias, String[] expectedOutputValues).  That method lets you override an input
alias variable with a hardcoded list of values. That way, the script doesn't actually have
to read that input variable from hdfs or cassandra. Then, it runs the script and checks the
specified output alias variable against the expected set of values.  It's a really nice way
to test your entire pig script with a single method call, but only IF your script has exactly
1 input and 1 output.  If you want to test more complicated scripts, you have to jump through
some hoops in order to override more input variables. But, it would be fairly easy to change
PigUnit so that it can override any number of inputs and check any number of outputs and do
so easily.  That's basically the change that I put into the base testing class I wrote. But,
it would be better to push that into PigUnit itself, and it's something that could easily
be done in an afternoon.
> 2) Update javadocs for the pig unit test classes to make them more readable.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message