[ https://issues.apache.org/jira/browse/PIG-1111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785419#action_12785419 ]
Chao Wang commented on PIG-1111: -------------------------------- Why we need build script change to run multiple outputs test cases? Are they any different from other test cases? I took a look at that part of change in the patch, seems nothing to do with the multiple outputs feature. > [Zebra] multiple outputs support > -------------------------------- > > Key: PIG-1111 > URL: https://issues.apache.org/jira/browse/PIG-1111 > Project: Pig > Issue Type: New Feature > Affects Versions: 0.6.0, 0.7.0 > Reporter: Gaurav Jain > Assignee: Gaurav Jain > Fix For: 0.6.0, 0.7.0 > > Attachments: PIG-1111.patch, PIG-1111.patch > > > Zebra enables application to stream data into different zebra table instances. > New Interface added: > setMultipleOutputs( JobConf jobconf, String commaSeparatedLocation, Class<? > extends ZebraOutputPartitioner> theClass. > Zebra maintains a list of tables instances based on commaseparatedlocations ( > in that order ) > ZebraOutputPartitioner interface has getOutputPartition method which is > implemented by the application. It will return an index into the list. Zebra > will write to that instance > We also introduce a new mapred property for setting multiple outputs. > mapred.lib.table.multi.output.dirs > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.