[
https://issues.apache.org/jira/browse/HBASE-12859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14294022#comment-14294022
]
Andrew Purtell edited comment on HBASE-12859 at 1/27/15 7:26 PM:
-----------------------------------------------------------------
bq. We do not differentiate or explicitly document this, but my understanding
of most of our InterfaceAudience.Public is for consumption, not for extending
or implementing interfaces (except for some coprocessor cases). So I think we
should be free to add new methods in Admin, Connection, etc in minor versions.
Shrug. So the Public/Stable annotation just means "keep this interface around,
don't worry about changes that will break an implementor?" . Then what would
Public/Evolving (or Unstable) mean as difference? Do we have what the
annotations mean documented somewhere? This point didn't come up in a review
when I backported client pushback, so now we have StatisticsHConnection. If
it's ok to add methods to HConnection I would like to sink the 0.98.10 RC that
has this change and fix it with a new patch/issue.
was (Author: apurtell):
bq. We do not differentiate or explicitly document this, but my understanding
of most of our InterfaceAudience.Public is for consumption, not for extending
or implementing interfaces (except for some coprocessor cases). So I think we
should be free to add new methods in Admin, Connection, etc in minor versions.
Shrug. So the Public/Stable annotation just means "keep this interface around,
don't worry about changes that will break an implementor?" . Then what would
Public/Unstable mean as difference? Do we have what the annotations mean
documented somewhere? This point didn't come up in a review when I backported
client pushback, so now we have StatisticsHConnection. If it's ok to add
methods to HConnection I would like to sink the 0.98.10 RC that has this change
and fix it with a new patch/issue.
> 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)
