[
https://issues.apache.org/jira/browse/ACCUMULO-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Tubbs updated ACCUMULO-3548:
----------------------------------------
Fix Version/s: (was: 1.8.0)
1.6.3
1.7.0
1.5.3
> Classes leaked through InstanceOperations into public API methods
> -----------------------------------------------------------------
>
> Key: ACCUMULO-3548
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3548
> Project: Accumulo
> Issue Type: Sub-task
> Components: client
> Reporter: Josh Elser
> Priority: Critical
> Fix For: 1.5.3, 1.7.0, 1.6.3
>
>
> 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)
