accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3548) Classes leaked through InstanceOperations into public API methods
Date Fri, 30 Jan 2015 19:27:35 GMT


Keith Turner commented on ACCUMULO-3548:

bq.  Does it make sense to pull a KeyExtent into the public API to just provide some stability

Maybe that has already been done?

bq.  it's really not "well consumed"


bq. should we try to make a better class which is well suited for public consumption in the
public API

We could deprecate methods that ref {{KeyExtent}} and replace with methods that use a class
that identifies a Tablet in a nicer way.

> Classes leaked through InstanceOperations into public API methods
> -----------------------------------------------------------------
>                 Key: ACCUMULO-3548
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: client
>            Reporter: Josh Elser
>            Priority: Critical
>             Fix For: 1.7.0
> Looking through ACCUMULO-3204, I noticed that we're (inadvertently?) using a few classes
in the public API without having them defined in the public API.
> {{connector.instanceOperations().getActiveScans()}} is what uses ActiveScan in the public
API. This provides a way for users to be relying on something that should be stable that doesn't
hold us to providing stability. ActiveScan also leaks Column and KeyExtent.
> * {{activeScan.getColumns()}}
> * {{activeScan.getExtent()}}
> It looks like {{ActiveCompaction}} does similar things.
> We should make sure these classes are in the public API (force us to ensure they stay

This message was sent by Atlassian JIRA

View raw message