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 01EA017E50 for ; Thu, 23 Oct 2014 04:25:35 +0000 (UTC) Received: (qmail 98040 invoked by uid 500); 23 Oct 2014 04:25:34 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 97999 invoked by uid 500); 23 Oct 2014 04:25:34 -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 97984 invoked by uid 99); 23 Oct 2014 04:25:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Oct 2014 04:25:34 +0000 Date: Thu, 23 Oct 2014 04:25:34 +0000 (UTC) From: "Josh Elser (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-3176) Add ability to create a table with user specified initial properties 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-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14181005#comment-14181005 ] Josh Elser commented on ACCUMULO-3176: -------------------------------------- bq. No, because it only solves one race condition. Sorry, I don't think I was clear. I meant to say it "helps mitigate", not implying that it solves the entire problem. More specifically, that the proposed changes here would help solve part of the problem. There is undeniably a bigger problem that needs solving. bq. It's not nasty if you can only set properties when it's offline. "nasty" was too colloquial on my part. I meant it as: only allowing table properties to change is a *very* drastic change WRT current user operations/expectations. It's certainly the least impactful code-change to solve the problem (read-as: zero code changes), but I would rather solve the larger issue in some way that doesn't require such a change. I'm not entirely sure of how we could do it though. > 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)