[
https://issues.apache.org/jira/browse/PHOENIX-4323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16257979#comment-16257979
]
Lars Hofhansl commented on PHOENIX-4323:
----------------------------------------
[~jamestaylor] above I was suggesting to append the 0 to the whatever the
region start key is when creating an index key.
Then as long as regionEndKey is >= regionStartKey|1 this can never happen.
Maybe we append 00 or 000. So the regionEndKey needs only be >=
regionStartKey|01 or >= regionStart|001, resp. Still possible to have this
problem, but increasingly unlikely.
Note that HBase can (and does) form shorter start/end key than keys in the
region, as long as the startKey is <= the first key and endKey is > the last
key.
> LocalIndexes could fail if your data row is not in the same region as your
> index region
> ---------------------------------------------------------------------------------------
>
> Key: PHOENIX-4323
> URL: https://issues.apache.org/jira/browse/PHOENIX-4323
> Project: Phoenix
> Issue Type: Bug
> Reporter: churro morales
> Assignee: Rajeshbabu Chintaguntla
> Attachments: LocalIndexIT.java
>
>
> This is not likely to happen, but if this does your data table and index
> write will never succeed.
> In HRegion.doMiniBatchMutation()
> You create index rows in the preBatchMutate() then when you call checkRow()
> on that index row the exception will bubble up if the index row is not in the
> same region as your data row.
> Like I said this is unlikely, but you would have to do a region merge to fix
> this issue if encountered.
> [~vincentpoon] has a test which he will attach to this JIRA showing an
> example how this can happen. The write will never succeed unless you merge
> regions if this ever happens.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
