hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12859) Major compaction completion tracker
Date Tue, 27 Jan 2015 18:37:34 GMT

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

Lars Hofhansl commented on HBASE-12859:
---------------------------------------

You're worried about binary compatibility? Someone who implemented HConnection directly? Both?
[~enis], what's your take on 1.0.x and 1.1.x? Per our new contract we can break binary compatibility
in a minor release (i.e. 1.1).

Would this break binary compatibility even? We'd add two new methods to the interface and
the (only) implementation class. Would code compiled against the old version break when executed
against a jar of the new version?

In any case, lemme get this into trunk first (and probably 1.1), and then discuss more on
0.98 and 1.0.

> Major compaction completion tracker
> -----------------------------------
>
>                 Key: HBASE-12859
>                 URL: https://issues.apache.org/jira/browse/HBASE-12859
>             Project: HBase
>          Issue Type: Brainstorming
>            Reporter: 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)

Mime
View raw message