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

James Taylor commented on PHOENIX-2737:
---------------------------------------

+1 for  second solution.

> Make sure local indexes work properly after fixing region overlaps by HBCK.
> ---------------------------------------------------------------------------
>
>                 Key: PHOENIX-2737
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2737
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Rajeshbabu Chintaguntla
>            Assignee: Rajeshbabu Chintaguntla
>             Fix For: 4.8.0
>
>
> When there are region overlaps hbck fix by moving hfiles of overlap regions 
> to new region of common key of overlap regions. Then we might not properly 
> replace region start key in HFiles in that case.  In this case we don't have 
> any relation of parent child region in hbase:meta so we cannot identify the 
> start key   in HFiles. To fix this we need to add separator after region 
> start key so that we can easily identify start key in HFile without always 
> touching hbase:meta. So when we create scanners for the Storefiles we can 
> check the region start key in hfile with region start key and if any change 
> we can just replace the old start key with current region start key. During 
> compaction we can properly replace the start key with actual key values.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to