Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DD8A81091E for ; Tue, 27 Jan 2015 19:41:36 +0000 (UTC) Received: (qmail 86900 invoked by uid 500); 27 Jan 2015 19:41:36 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 86827 invoked by uid 500); 27 Jan 2015 19:41:36 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 86717 invoked by uid 99); 27 Jan 2015 19:41:36 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Jan 2015 19:41:36 +0000 Date: Tue, 27 Jan 2015 19:41:36 +0000 (UTC) From: "Andrew Purtell (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-12859) Major compaction completion tracker MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-12859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14294050#comment-14294050 ] Andrew Purtell commented on HBASE-12859: ---------------------------------------- We don't actually have a 1.0 release yet so could still make this change there. I see no problem with you making HConnection changes in 0.98 should HBASE-12932 be acceptable. > Major compaction completion tracker > ----------------------------------- > > Key: HBASE-12859 > URL: https://issues.apache.org/jira/browse/HBASE-12859 > Project: HBase > Issue Type: Brainstorming > Reporter: Lars Hofhansl > Assignee: Lars Hofhansl > Attachments: 12859-v1.txt, 12859-v2.txt, 12859-v3.txt, 12859-v4.txt, 12859-v5.txt, 12859-wip-UNFINISHED.txt > > > In various scenarios it is helpful to know a guaranteed timestamp up to which all data in a table was major compacted. > We can do that keeping a major compaction timestamp in META. > A client then can iterate all region of a table and find a definite timestamp, which is the oldest compaction timestamp of any of the regions. > [~apurtell], [~ghelmling], [~giacomotaylor]. -- This message was sent by Atlassian JIRA (v6.3.4#6332)