[
https://issues.apache.org/jira/browse/PIG-1292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12844724#action_12844724
]
Xuefu Zhang commented on PIG-1292:
----------------------------------
Looking at the OrderedLoadFunc interface, public WritableComparable<?>
getSplitComparable(InputSplit split, int splitIdx), I am not sure why split
index suddenly comes into the picture. Though it was in earlier discussion
between Pig and Zebra, we agree that this is very implementation specific,
which shouldn't dictate API design. Thus, I don't think that split index should
be in the signature even if it helps Zebra implementation. If an implementation
needs the split index, it can always store the index in the split it generates.
That's what exactly Zebra plan to do.
> Interface Refinements
> ---------------------
>
> Key: PIG-1292
> URL: https://issues.apache.org/jira/browse/PIG-1292
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.7.0
> Reporter: Ashutosh Chauhan
> Assignee: Ashutosh Chauhan
> Fix For: 0.7.0
>
> Attachments: pig-1292.patch, pig-interfaces.patch
>
>
> A loader can't implement both OrderedLoadFunc and IndexableLoadFunc, as both
> are abstract classes instead of being interfaces.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
