accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Marion (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-2336) support user-defined table metadata
Date Fri, 07 Feb 2014 01:54:19 GMT


Dave Marion commented on ACCUMULO-2336:

I remember a discussion a while back about storing application metadata in Accumulo somewhere,
like in the properties. Very similiar to this issue. It was shot down because the of the potential
size of the properties, the properties are stored in ZK, and we don't want to overuse ZK.
The suggestion at the time was to have the application maintain the metadata in another table.
I guess another alternative is to encode the metadata in a set of keys that the application
doesn't expose to the users.

> 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