Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Fri, 7 Feb 2014 04:09:20 +0000 (UTC)
From: "Christopher Tubbs (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12693769.1391728620804.2363.1391746160188@arcas>
In-Reply-To: <JIRA.12693769.1391728620804@arcas>
References: <JIRA.12693769.1391728620804@arcas>
Subject: [jira] [Commented] (ACCUMULO-2336) support user-defined table
 metadata
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ACCUMULO-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894182#comment-13894182 ] 

Christopher Tubbs commented on ACCUMULO-2336:
---------------------------------------------

>From an API perspective, one way to do this without changing internal details:

{code:java}
public class ApplicationTable extends org.apache.accumulo.client.api.Table {

  public ApplicationTable(String name, Properties applicationMetadata) {
    super(name); // create new table
    updateApplicationMetadata(applicationMetadata);
  }

  private void updateApplicationMetadata(Properties appData) {
    /* implementation */
  }

}
{code}

This depends on a good, extensible client API with usable Table objects that an application could extend.

> support user-defined table metadata
> -----------------------------------
>
>                 Key: ACCUMULO-2336
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2336
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: Adam Fuchs
>
> An Accumulo table can have all sorts of external information that applications use to interact with the table. One example is schema definition. Another might be information about what data or data sources have been loaded into the table. It would be nice to encapsulate all of this information together with the table's data for easier management, particularly when cloning tables or discovering tables that are shared across applications (multi-tenancy).
> How can we support generic table metadata properties so that users can innovate independently? These could be accessible via the table properties, or this could be a separate set of public API methods if appropriate.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)