accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3176) Add ability to create a table with user specified initial properties
Date Thu, 23 Oct 2014 14:51:33 GMT

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

Keith Turner commented on ACCUMULO-3176:
----------------------------------------

Its a bit clunky, but users can currently get a good deal of consistency w/ clone table. 
The API call to clone a table allows a user to set per table props before the clone is created.
 So if a user really wants to ensure a particular per table config is seen by all tablets
at the same time they could do the following.

 # clone table T1 to T1_tmp  w/ new per table props
 # delete table T1
 # rename T1_tmp to T1  

Of course this would be disruptive to anything using T1.

This discussion made me wonder what the javadocs for setProperty say.  Currenty says the following
:

bq. Sets a property on a table. Note that it may take a short period of time (a second) to
propagate the change everywhere.

Maybe this should be expanded to state that tablets may see the config change at different
times and explicitly state that its an async operation.  

> Add ability to create a table with user specified initial properties
> --------------------------------------------------------------------
>
>                 Key: ACCUMULO-3176
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3176
>             Project: Accumulo
>          Issue Type: Sub-task
>            Reporter: Jenna Huston
>            Assignee: Jenna Huston
>
> This change would allow for table properties to be set before the default tablet is created.
 Instead of just adding a new create method, a NewTableConfiguration class could be created
and passed and the other create methods deprecated.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message