You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Vincent Poon (JIRA)" <ji...@apache.org> on 2017/10/25 22:42:00 UTC

[jira] [Comment Edited] (PHOENIX-4323) LocalIndexes could fail if your data row is not in the same region as your index region

    [ https://issues.apache.org/jira/browse/PHOENIX-4323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16219684#comment-16219684 ] 

Vincent Poon edited comment on PHOENIX-4323 at 10/25/17 10:41 PM:
------------------------------------------------------------------

Test to reproduce the issue: testIndexRowDifferentRegion()


was (Author: vincentpoon):
Test to reproduce the issue

> 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)