accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Marion (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3089) Create a volume chooser that makes decisions based on table attributes
Date Wed, 01 Oct 2014 16:49:35 GMT

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

Dave Marion commented on ACCUMULO-3089:
---------------------------------------

bq. 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.

Looking at the bylaws[1], this isn't a veto, it's an objection. The ASF community concensus
building guide[2] appear to back this up. However, our bylaws state that a vote must take
place since an objection has been raised. I'd like to prevent that by trying to understand
the details behind the proposed alternative. If we can't get our questions answered here,
how will changing the communication mechanism help?

[1] http://accumulo.apache.org/bylaws.html#CTR
[2] https://community.apache.org/committers/consensusBuilding.html

> 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)

Mime
View raw message