cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Masters (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4871) get_paged_slice does not obey SlicePredicate
Date Wed, 31 Jul 2013 15:19:48 GMT

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

Adam Masters commented on CASSANDRA-4871:
-----------------------------------------

Looking at the word_count example in github, its interesting to note the comment which has
been added against the wide-row functionality: "this will cause the predicate to be ignored
in favor of scanning everything as a wide row". This suggests that ignoring the SlicePredicate
for wide rows is by design. In which case, how does one limit the columns when using wide
rows?
                
> get_paged_slice does not obey SlicePredicate
> --------------------------------------------
>
>                 Key: CASSANDRA-4871
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4871
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API, Hadoop
>    Affects Versions: 1.1.0
>            Reporter: Scott Fines
>            Priority: Minor
>         Attachments: CASSANDRA-4816.patch
>
>
> When experimenting with WideRow support, I noticed that it is not possible to specify
a bounding SlicePredicate. This means that, no matter what you may wish, the entire Column
Family will be used during a get_paged_slice call. This is unfortunate, if (for example) you
are attempting to do MapReduce over a subset of your column range.
> get_paged_slice should support a SlicePredicate, which will bound the column range over
which data is returned. It seems like this SlicePredicate should be optional, so that existing
code is not broken--when the SlicePredicate is not specified, have it default to going over
the entire column range.

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

Mime
View raw message