[
https://issues.apache.org/jira/browse/PHOENIX-1561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14259457#comment-14259457
]
Brian Johnson commented on PHOENIX-1561:
----------------------------------------
You're right, I completely forgot about that. I was thinking that
OrderedLoadFunc just worked because the data is sorted. The implementation in
HBaseStorage is pretty trivial because it just wraps the
org.apache.hadoop.hbase.mapreduce.TableSplit. I assume the Phoenix
implementation would be identical, but I'm not familiar enough with the Phoenix
loader to be sure.
> Pig optimized joins
> -------------------
>
> Key: PHOENIX-1561
> URL: https://issues.apache.org/jira/browse/PHOENIX-1561
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.2
> Reporter: Brian Johnson
> Assignee: Brian Johnson
> Attachments: patch
>
>
> PhoenixHBaseLoader should implement both OrderedLoadFunc and
> CollectableLoadFunc just like HBaseStorage. There is nothing special that
> needs to be done other than implementing a single method. As in HBaseStorage,
> it is up to the user to ensure that the required constraints are not
> violated.
> {code:java}
> public void ensureAllKeyInstancesInSameSplit() throws IOException {
> /**
> * no-op because hbase keys are unique
> * This will also work with things like
> DelimitedKeyPrefixRegionSplitPolicy
> * if you need a partial key match to be included in the split
> */
> LOG.debug("ensureAllKeyInstancesInSameSplit");
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
