Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2C6A011725 for ; Sat, 5 Apr 2014 13:23:20 +0000 (UTC) Received: (qmail 1836 invoked by uid 500); 5 Apr 2014 13:23:19 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 1753 invoked by uid 500); 5 Apr 2014 13:23:16 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 1743 invoked by uid 99); 5 Apr 2014 13:23:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 05 Apr 2014 13:23:14 +0000 Date: Sat, 5 Apr 2014 13:23:14 +0000 (UTC) From: "Christopher Tubbs (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (ACCUMULO-2634) Allow options through public API for table creation MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-2634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Tubbs updated ACCUMULO-2634: ---------------------------------------- Issue Type: Sub-task (was: Improvement) Parent: ACCUMULO-2589 > 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}} object we'd want TableOperations to accept. -- This message was sent by Atlassian JIRA (v6.2#6252)