hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12478) HBASE-10141 and MIN_VERSIONS are not compatible
Date Sat, 15 Nov 2014 03:45:34 GMT

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

Hudson commented on HBASE-12478:
--------------------------------

SUCCESS: Integrated in HBase-0.98-on-Hadoop-1.1 #645 (See [https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/645/])
HBASE-12478 HBASE-10141 and MIN_VERSIONS are not compatible (tedyu: rev 835490e3b25c0d9923867461c173a123d06edd0c)
* hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HStore.java
* hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestStore.java


> HBASE-10141 and MIN_VERSIONS are not compatible
> -----------------------------------------------
>
>                 Key: HBASE-12478
>                 URL: https://issues.apache.org/jira/browse/HBASE-12478
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Enis Soztutar
>            Assignee: Ted Yu
>            Priority: Critical
>             Fix For: 2.0.0, 0.98.8, 0.99.2
>
>         Attachments: 12478-0.98.patch, 12478-v1.txt, 12478-v2.txt
>
>
> HBASE-10141 is a good optimization, eliminating the need to scan already expired files
(through TTL). However, I think if MIN_VERSIONS is set, it will not ensure that there will
be at least that many versions since it bypasses the scan layer. 
> I think we can just do a simple check before the HBASE-10141 optimization to see whether
MIN_VERSIONS is set for the table, and if so just do the regular old way of doing the scan
in the compaction. 



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

Mime
View raw message