You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (Created) (JIRA)" <ji...@apache.org> on 2012/01/25 19:55:40 UTC
[jira] [Created] (CASSANDRA-3785) Support slice with exclusive
start and stop
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
Fix For: 1.2
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
[jira] [Assigned] (CASSANDRA-3785) Support slice with exclusive
start and stop
Posted by "Sylvain Lebresne (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sylvain Lebresne reassigned CASSANDRA-3785:
-------------------------------------------
Assignee: Sylvain Lebresne
> 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.2
>
> 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
[jira] [Commented] (CASSANDRA-3785) Support slice with exclusive
start and stop
Posted by "Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194803#comment-13194803 ]
Jonathan Ellis commented on CASSANDRA-3785:
-------------------------------------------
Why does composite-ness matter here? Isn't it decomposing into the same slice calls either way?
> 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
[jira] [Updated] (CASSANDRA-3785) Support slice with exclusive
start and stop
Posted by "Sylvain Lebresne (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sylvain Lebresne updated CASSANDRA-3785:
----------------------------------------
Attachment: 3785.patch
> 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.2
>
> 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
[jira] [Updated] (CASSANDRA-3785) Support slice with exclusive
start and stop
Posted by "Sylvain Lebresne (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sylvain Lebresne updated CASSANDRA-3785:
----------------------------------------
Issue Type: Sub-task (was: Improvement)
Parent: CASSANDRA-3761
> Support slice with exclusive start and stop
> -------------------------------------------
>
> Key: CASSANDRA-3785
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3785
> Project: Cassandra
> Issue Type: Sub-task
> 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
[jira] [Updated] (CASSANDRA-3785) Support slice with exclusive
start and stop
Posted by "Jonathan Ellis (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis updated CASSANDRA-3785:
--------------------------------------
Reviewer: jbellis
> Support slice with exclusive start and stop
> -------------------------------------------
>
> Key: CASSANDRA-3785
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3785
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Labels: cql3
> Fix For: 1.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
[jira] [Commented] (CASSANDRA-3785) Support slice with exclusive
start and stop
Posted by "Sylvain Lebresne (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (CASSANDRA-3785) Support slice with exclusive
start and stop
Posted by "Jonathan Ellis (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251106#comment-13251106 ]
Jonathan Ellis commented on CASSANDRA-3785:
-------------------------------------------
+1
> Support slice with exclusive start and stop
> -------------------------------------------
>
> Key: CASSANDRA-3785
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3785
> Project: Cassandra
> Issue Type: Sub-task
> Components: Core
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Labels: cql3
> Fix For: 1.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
[jira] [Commented] (CASSANDRA-3785) Support slice with exclusive
start and stop
Posted by "Sylvain Lebresne (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CASSANDRA-3785?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13193228#comment-13193228 ]
Sylvain Lebresne commented on CASSANDRA-3785:
---------------------------------------------
For CQL, we can likely get around by asking one more column and removing manually columns after the query to transform an inclusive into an exclusive. It does sound a little lame to me that we don't support this internally though (but I could leave with that).
> 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
> Labels: cql3
> Fix For: 1.2
>
>
> 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