phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-4323) LocalIndexes could fail if your data row is not in the same region as your index region
Date Thu, 02 Nov 2017 05:24:01 GMT

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

James Taylor commented on PHOENIX-4323:
---------------------------------------

Like I commented before, whether adding a 0 byte helps or not depends on the row key. It's
not clear if this makes things very much unlikely. You need to consider the data table schema.
We should think more on this one.

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

Mime
View raw message