accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2634) Allow options through public API for table creation
Date Tue, 29 Apr 2014 17:56:15 GMT

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

Josh Elser commented on ACCUMULO-2634:
--------------------------------------

The ability to set TablePermissions atomically would also be desirable (before createTable
returns, I want a user to have a permission granted). This would prevent the try/catch/retry
in the invoking code for security exceptions.

> Allow options through public API for table creation
> ---------------------------------------------------
>
>                 Key: ACCUMULO-2634
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2634
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: client
>            Reporter: Josh Elser
>             Fix For: 1.7.0
>
>
> In debugging a test, I found myself in {{CreateTableCommand}}. The {{evc}} option will
automatically set the {{VisibilityConstraint}} on the newly created table by doing the following:
> {code}
>   createtable()
>   addConstraint()
> {code}
> This approach has a subtle race condition. The tabletserver hosting the tablet for the
newly created table might not see the table option update that occurs as a part of addConstraint.
This means the above two commands may both successfully return but the client has the ability
to data that doesn't satisfy the constraint until the tserver's table configuration observer
sees the update.
> Thankfully, the CreateTable fate op has the ability to pass in a set of properties for
a table. The TableOperationsImpl class generates the default set of table properties, but
we should also allow users to provide their own options that can override these defaults.
> [~billie.rinaldi] also had the idea to create some helper methods that would simplify
the API for making configuring IteratorSettings and Constraints to the generic {{Map<String,String>}}
object we'd want TableOperations to accept.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message