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 64EE4175C2 for ; Mon, 29 Sep 2014 16:11:35 +0000 (UTC) Received: (qmail 52956 invoked by uid 500); 29 Sep 2014 16:11:35 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 52925 invoked by uid 500); 29 Sep 2014 16:11:35 -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 52909 invoked by uid 99); 29 Sep 2014 16:11:35 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Sep 2014 16:11:35 +0000 Date: Mon, 29 Sep 2014 16:11:35 +0000 (UTC) From: "Bill Havanki (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-3089) Create a volume chooser that makes decisions based on table attributes 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-3089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14151849#comment-14151849 ] Bill Havanki commented on ACCUMULO-3089: ---------------------------------------- It doesn't seem that any progress is being made on resolving Sean's veto on this ticket. I suggest some other means of communication where back-and-forth is easier. IMO, a veto on a ticket would apply to its subtasks. Otherwise, a veto could be avoided by making subtasks constituting the identical work (unless the original vetoer then vetoes those, which starts getting silly). I think Sean's early veto was meant to try to save folks time working on an implementation of this ticket's idea that would ultimately not be committed. It could certainly still be worked on, hosted elsewhere, and all that, and the veto resolved at some other time. Again, though, it seems better communication would be needed. > Create a volume chooser that makes decisions based on table attributes > ---------------------------------------------------------------------- > > Key: ACCUMULO-3089 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3089 > Project: Accumulo > Issue Type: Improvement > Reporter: Christopher Tubbs > Assignee: Jenna Huston > > Use case: > User provisions multiple volumes, some with tmpfs drives, some with SSDs, some with traditional magnetic spindle hard drives. A volume chooser could use attribute information on tables (ACCUMULO-2841) to decide which volume to choose when creating new tablets. -- This message was sent by Atlassian JIRA (v6.3.4#6332)