Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Wed, 3 Apr 2013 20:23:15 +0000 (UTC)
From: "William Slacum (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12639854.1364580547367.101280.1365020595557@arcas>
In-Reply-To: <JIRA.12639854.1364580547367@arcas>
References: <JIRA.12639854.1364580547367@arcas>
Subject: [jira] [Commented] (ACCUMULO-1228) Allow clients to disable column
 families and locality groups
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

William Slacum commented on ACCUMULO-1228:
------------------------------------------

Why even have the locality group defined that way in the first place then? It seems brittle if we require a client to apply labels to sets of column families (that maybe have to be mutually exclusive across lables?) and then never use them. How does the system handle querying today if a locality group is inconsistent across RFiles? I'd more prefer to have a consistent API for creation and use. If we don't allow a user to query based on locality group name, then we shouldn't have them specify it in the first place. Likewise, if we require them to specify it at creation time, then they should be able to query using it. Having one without the other makes it kind of useless.
                
> Allow clients to disable column families and locality groups
> ------------------------------------------------------------
>
>                 Key: ACCUMULO-1228
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1228
>             Project: Accumulo
>          Issue Type: New Feature
>          Components: client, tserver
>    Affects Versions: 1.5.0
>            Reporter: William Slacum
>            Priority: Minor
>             Fix For: 1.6.0
>
>
> There's an inconsistency between what a server is capable of and what a client can tell it to do with respect to fetching column families.
> Currently, a user can tell a {{Scanner}} to fetch some set of column families. The iterators support not only this, but also the converse where a user does not want to retrieve column families. An iterator implementation can do this by hand, but a client cannot specifically tell a Scanner to not return data from a set of column families. Clients should be able to specify this option.
> There also seems to be an inconsistency with how locality groups are defined and then utilized. If I want to specify a set of column families as being part of a locality group, I have to provide a mapping of locality group name to a list of column families. If I want to fetch a locality group, I have to get the mapping first, rather than just set which locality group I want to use. It'd be more convenient to tell the scanner just to fetch which locality groups I want, and have the server know which column families that means.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira