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

Andrew Purtell edited comment on HBASE-12859 at 1/27/15 7:02 PM:
-----------------------------------------------------------------

It's more of a policy question. The HConnection interface is marked 
Public/Stable. For the client pushback backport I added a 
"StatisticsHConnection" that extends HConnection and changed the implementation 
in HConnectionManager to implement StatisticsHConnection for this reason. On 
the off chance someone does do something with HConnection, they won't be 
affected. For your changes I don't see a concern, don't add the methods to the 
interface, just add them to the implementation, and cast. This does have 
implications, just like the other change, if someone wants to provide an 
alternate HConnection back to HBase, but it maintains the policy implied by the 
interface annotation...


was (Author: apurtell):
It's more of a policy question. The HConnection interface is marked 
Public/Stable. For the client pushback backport I added a 
"StatisticsHConnection" that extends HConnection and changed the implementation 
in HConnectionManager to implement StatisticsHConnection for this reason. On 
the off chance someone does do something with HConnection, they won't be 
affected. For your changes I don't see a concern, don't add the methods to the 
interface, just add them to the implementation, and cast. 

> 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)

Reply via email to