[ACCUMULO-3548] Classes leaked through InstanceOperations into public API methods

• Type: Sub-task
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 1.7.0
• Component/s: client
• Assignee: Keith Turner
• Reporter: Josh Elser
• Created: 30/Jan/15 16:25
• Updated: 03/Jun/16 18:05
• Resolved: 27/Apr/15 21:54

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).

Issue Links

• is related to: ACCUMULO-3657 API Specification is incomplete
• relates to: ACCUMULO-3488 KeyExtent used in the public API, but not documented as such in README
• links to: GitHub Pull Request #28