accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3089) Create a volume chooser that makes decisions based on table attributes
Date Fri, 26 Sep 2014 18:14:34 GMT


Sean Busbey commented on ACCUMULO-3089:

 In particular, I explained that your "simpler approach" is practically identical to what
is proposed. This is an implementation of precisely that sort of thing. You never replied
with any disagreement, or explanation of how you thought they were different.

Just as a simple example, limiting volumes to particular namespaces would not require changing
when table properties are available. It would also not require changing the table creation

Also, just a small point of order here: you can veto a commit, but you can't veto an idea
or a contribution. As it stands, I see your "-1" as blocking this patch from being committed,
but not the refinement, discussion, and review, of this contribution to the community. As
long as your veto stands, it can't be commited to Accumulo, so maybe Jenna will have to host
it somewhere else, but my hope is that you'll change your veto once you take a look at the
change and realize it achieves precisely the sort of thing that you prefer "like limiting
particular namespaces to particular volumes", especially since I believe your veto was based
on a misunderstanding of this being scoped around heterogeneous storage.

Sure, I suppose that is technically true. I just want to make sure no one is confused about
vetos needing to be expressly revoked by the vetoer.

For the record, my veto is not based on a misunderstanding.

> Create a volume chooser that makes decisions based on table attributes
> ----------------------------------------------------------------------
>                 Key: ACCUMULO-3089
>                 URL:
>             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

View raw message