accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3906) Drop the ability to filter column qualifiers natively in the scanner
Date Thu, 25 Jun 2015 21:04:04 GMT

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

Christopher Tubbs commented on ACCUMULO-3906:
---------------------------------------------

Kind of thinking CF projection shouldn't be a first-class citizen either... if CQ projection
isn't. Might be better to make Scanner minimalistic... essentially with setRange() and addIterator(),
and make sure we have a comprehensive bag of iterators to pick from and are easily chained
together.

> Drop the ability to filter column qualifiers natively in the scanner
> --------------------------------------------------------------------
>
>                 Key: ACCUMULO-3906
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3906
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: client
>            Reporter: Christopher Tubbs
>            Assignee: Christopher Tubbs
>             Fix For: 2.0.0
>
>
> In the new API, it should not contain the ability to specify a column filter natively,
using a built-in feature. This filtering should be conveniently available as a user iterator,
rather than built-in in the system iterators.
> This would make column qualifier filtering more consistent with other filtering, and
would avoid problems like those seen in ACCUMULO-3905.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message