[ https://issues.apache.org/jira/browse/PIG-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12733311#action_12733311 ]
Arun C Murthy commented on PIG-878: ----------------------------------- bq. Should note also that I didn't add any tests because this was a fix for existing functionality, and frankly I'm not exactly sure how to test it. We could check the #splits returned by the slicer to ensure it's equal to the replication factor of the input files? > Pig is returning too many blocks in the InputSplit > -------------------------------------------------- > > Key: PIG-878 > URL: https://issues.apache.org/jira/browse/PIG-878 > Project: Pig > Issue Type: Bug > Affects Versions: 0.3.0 > Reporter: Alan Gates > Assignee: Alan Gates > Priority: Critical > Fix For: 0.4.0 > > Attachments: PIG-878.patch > > > When SlicerWrapper builds a slice, it currently returns the 3 locations for > every block in the file it is slicing, instead of the 3 locations for the > block covered by that slice. This means Pig's odds of having its maps placed > on nodes local to the data goes way down. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.