[
https://issues.apache.org/jira/browse/ACCUMULO-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser updated ACCUMULO-1228:
---------------------------------
Fix Version/s: (was: 1.7.0)
1.8.0
> 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.8.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 was sent by Atlassian JIRA
(v6.3.4#6332)
