accumulo-notifications mailing list archives

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


Josh Elser commented on ACCUMULO-3548:

Another option is to advertise that these objects are subject to change, but I feel like that's
an insufficient solution because there isn't no "recommended stable" way to do them. These
methods were added for user consumption, we should make sure that they're actually stable.

> 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, KeyExtent, ScanType and ScanState.
> * {{activeScan.getColumns()}}
> * {{activeScan.getExtent()}}
> * {{activeScan.getType()}}
> * {{activeScan.getState()}}
> It looks like {{ActiveCompaction}} does similar things. {{TimeType}} is also used {{NewTableConfiguration}}.
> 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