accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3177) Create a per table volume chooser
Date Fri, 24 Oct 2014 20:52:35 GMT


Christopher Tubbs commented on ACCUMULO-3177:

bq. it allows any user with ALTER TABLE to change how the system manages hdfs internals

This is already true for a great many HDFS parameters, such as replication, block size, durability,
etc. The chooser is further removed from those things, since it at least keeps things at the
Accumulo layer of abstraction rather than HDFS internals, because the focus of this issue
is to specify a class to do the volume choosing for a particular table. It has little to do
with HDFS... only Accumulo volumes.

bq. namespaces property altering can be limited to a much smaller set of trusted individuals

Table-level properties always override namespace-level properties, and it is presumed that
more people will have permissions to alter a table's properties than will have namespace-level
permissions, which it seems you are acknowledging by mentioning that it's common to have ALTER
TABLE, so I'm not sure what you're suggesting here. Unless... are you suggesting that we create
namespace-only properties, which cannot be set/overridden at the per-table level? Because
that would be a *huge* change to re-work all the configuration internals.

In any case, I think there's merit to having a first pass not require ACCUMULO-3176, by setting
the parameter at the namespace level rather than at table creation. I don't think there's
any reason to explicitly prevent a per-table property being set for this, though.

> Create a per table volume chooser
> ---------------------------------
>                 Key: ACCUMULO-3177
>                 URL:
>             Project: Accumulo
>          Issue Type: Sub-task
>            Reporter: Jenna Huston
>            Assignee: Jenna Huston
> This chooser would decide on a per table basis what VolumeChooser to use when creating
new tablets.

This message was sent by Atlassian JIRA

View raw message