[
https://issues.apache.org/jira/browse/PHOENIX-4323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16222697#comment-16222697
]
Lars Hofhansl commented on PHOENIX-4323:
----------------------------------------
We can make this less likely by appending a 0 after the region start key,
before appending all the rest.
I.e. now we do something like regionkey|rest, we could do regionkey|0|rest. It
would still be possible to have this scenario, just much less likely.
We could also have a split policy for this and or make sure that is in this
case the regionEndKey and at least regionStartKey | 255.
In these cases, though, we run the risk of very large regions.
> 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: Vincent Poon
> 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)
