Details
-
Sub-task
-
Status: Resolved
-
Normal
-
Resolution: Fixed
Description
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