accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-2336) support user-defined table metadata
Date Fri, 07 Feb 2014 04:09:20 GMT


Christopher Tubbs commented on ACCUMULO-2336:

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

public class ApplicationTable extends org.apache.accumulo.client.api.Table {

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

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


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:
>             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

View raw message