[
https://issues.apache.org/jira/browse/CASSANDRA-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194811#comment-13194811
]
Sylvain Lebresne commented on CASSANDRA-3785:
---------------------------------------------
Because composites have a end-of-component byte with each component that allow
to respect inclusiveness/exclusiveness at query time so they don't need that
"trick".
> Support slice with exclusive start and stop
> -------------------------------------------
>
> Key: CASSANDRA-3785
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3785
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Labels: cql3
> Fix For: 1.1
>
> Attachments: 3785.patch
>
>
> Currently, slices are always start and end inclusive. However, for CQL 3.0,
> we already differenciate between inclusivity/exclusivity for the row key and
> for the component of composite columns. It would be nice to always support
> that distinction.
--
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
