[
https://issues.apache.org/jira/browse/CASSANDRA-3982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13273684#comment-13273684
]
Jonathan Ellis commented on CASSANDRA-3982:
-------------------------------------------
This makes sense to me, primarily because CQL3 divorces the logical row from
the physical row, so "checking all columns" is a reasonable price to pay now
where before it was not.
bq. a solution to that will be to introduce 'IS NOT NULL' (#3783)
How would that address this?
> Explore not returning range ghosts
> ----------------------------------
>
> Key: CASSANDRA-3982
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3982
> Project: Cassandra
> Issue Type: Sub-task
> Components: API
> Affects Versions: 1.1.0
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Labels: cql3
> Fix For: 1.1.1
>
> Attachments: 3982.txt
>
>
> This ticket proposes to remove range ghosts in CQL3.
> The basic argument is that range ghosts confuses users a lot and don't add
> any value since range ghost don't allow to distinguish between the two
> following case:
> * the row is deleted
> * the row is not deleted but don't have data for the provided filter
--
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
