accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-4427) TabletBalancer API broken in 1.7
Date Fri, 26 Aug 2016 16:38:20 GMT

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

Sean Busbey commented on ACCUMULO-4427:
---------------------------------------

definitely not public api, at least according to our spec. maybe it's time we expressly annotate
our public facing api so these kinds of changes aren't surprising for folks who decide to
use the non-public pluggable bits?

is there a way we can update the TableBalancer API so that it continues working for both 1.6
and 1.7 users as of some future release?

> TabletBalancer API broken in 1.7
> --------------------------------
>
>                 Key: ACCUMULO-4427
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-4427
>             Project: Accumulo
>          Issue Type: Bug
>          Components: client, master
>            Reporter: John Vines
>
> In 1.6, the TabletBalancer APIs used org.apache.accumulo.core.data.KeyExtent. In 1.7,
this class was deprecated in favor of TabletId. Unfortunately with this change, the TabletBalancer
API was updated to use org.apache.accumulo.core.data.impl.KeyExtent. This causes compile time
issues with balancers from 1.6.
> I'm not sure if the TabletBalancer is technically part of the public API, but given this
is a user pluggable space I would expect some degree of stability, at least between two versions.



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

Mime
View raw message