You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Rajeshbabu Chintaguntla (JIRA)" <ji...@apache.org> on 2015/04/28 21:46:07 UTC

[jira] [Updated] (HBASE-13431) Allow to skip store file range check based on column family while creating reference files in HRegionFileSystem#splitStoreFile

     [ https://issues.apache.org/jira/browse/HBASE-13431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rajeshbabu Chintaguntla updated HBASE-13431:
--------------------------------------------
    Summary: Allow to skip store file range check based on column family while creating reference files in HRegionFileSystem#splitStoreFile  (was: Move splitStoreFile to SplitTransaction interface to allow creating both reference files in case required)

> Allow to skip store file range check based on column family while creating reference files in HRegionFileSystem#splitStoreFile
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-13431
>                 URL: https://issues.apache.org/jira/browse/HBASE-13431
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Rajeshbabu Chintaguntla
>            Assignee: Rajeshbabu Chintaguntla
>             Fix For: 2.0.0, 1.1.0
>
>         Attachments: HBASE-13431.patch, HBASE-13431_v2.patch, HBASE-13431_v3.patch, HBASE-13431_v4.patch
>
>
>  APPROACH #3 at PHOENIX-1734 helps to implement local indexing without much changes in HBase. For split we need one kernel change to allow creating both top and bottom reference files for index column family store files even when the split key not in the storefile key range. 
> The changes helps in this case are  
> 1) pass boolean to HRegionFileSystem#splitStoreFile to allow to skip the storefile key range check.
> 2) move the splitStoreFile with extra boolean parameter  to the new interface introduced at HBASE-12975. 



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