accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-3548) Classes leaked through InstanceOperations into public API methods
Date Fri, 30 Jan 2015 19:03:35 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Josh Elser updated ACCUMULO-3548:
---------------------------------
    Description: 
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 stable).

  was:
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 stable).


> Classes leaked through InstanceOperations into public API methods
> -----------------------------------------------------------------
>
>                 Key: ACCUMULO-3548
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3548
>             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
stable).



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

Mime
View raw message