[
https://issues.apache.org/jira/browse/PHOENIX-4323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238540#comment-16238540
]
James Taylor commented on PHOENIX-4323:
---------------------------------------
[~rajeshbabu] - though the test is contrived, this could potentially happen if
local index rows appear *after* data table rows. Any thoughts on how to best
prevent this? Can the split policy handle this?
> 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
> Priority: Major
> 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)
