[
https://issues.apache.org/jira/browse/CASSANDRA-3742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-3742:
----------------------------------------
Attachment: 3742.patch
Attaching patch implementing the idea described above (includes a unit test).
Note that when this option is used the patch does not trim the result
post-reconciliation of the result of the different replicas. The reason being
that this can be done more simply and more efficiently on the CQL side (i.e,
after the creation of the CqlResult object).
> Allow to do a range slice with a limit on the number of column across all rows
> ------------------------------------------------------------------------------
>
> Key: CASSANDRA-3742
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3742
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: Sylvain Lebresne
> Fix For: 1.1
>
> Attachments: 3742.patch
>
>
> The proposal is to add a new max_columns option to RangeSliceCommand so that
> as to bound the total amount of columns returned rather than just the number
> of keys. In that case, the SlicePredicate.count would thus be ignored.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
