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

["Sergey Soldatov (JIRA)" <ji...@apache.org>]

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

Sergey Soldatov commented on PHOENIX-4323:
------------------------------------------

Well, by design local index data should be stored in the same region all the time. But it's quite interesting case when in the region there is room for a single rowkey only. Ping [~rajeshbabu]

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