Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Thu, 9 Apr 2015 18:28:13 +0000 (UTC)
From: "Christopher Tubbs (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12771373.1422635136000.43417.1428604093363@Atlassian.JIRA>
In-Reply-To: <JIRA.12771373.1422635136000@Atlassian.JIRA>
References: <JIRA.12771373.1422635136000@Atlassian.JIRA>
 <JIRA.12771373.1422635136803@arcas>
Subject: [jira] [Updated] (ACCUMULO-3548) Classes leaked through
 InstanceOperations into public API methods
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Christopher Tubbs updated ACCUMULO-3548:
----------------------------------------
    Issue Type: Sub-task  (was: Bug)
        Parent: ACCUMULO-3657

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