You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We would like to perform range deletes but that is not supported.
DELETE FROM test.journal WHERE
persistence_id = 'a' AND
partition_nr = 1 AND
sequence_nr >= 0 AND
sequence_nr <= 17;
InvalidRequest: Error from server: code=2200 [Invalid query] message="Only EQ relation is supported on the partition key for now for DELETE statements"
A less efficient alternative would be to delete each row separately, but that doesn't behave in the same way as Apache Cassandra.
DELETE FROM test.journal WHERE
persistence_id = 'a' AND
partition_nr = 1 AND
sequence_nr = 1;
InvalidRequest: Error from server: code=2200 [Invalid query] message="Some clustering keys are missing"
The missing clustering key is the timestamp. Apache Cassandra doesn't require that all clustering keys are defined for deletes.
A workaround for that could be to not have the timestamp as a clustering key for CosmosDB. I still think we should have it for Cassandra because it's nice that we don't overwrite when accidentally using same pid/seqnr.
We also have the timebucket, but that can be removed #399
The text was updated successfully, but these errors were encountered:
We would like to perform range deletes but that is not supported.
A less efficient alternative would be to delete each row separately, but that doesn't behave in the same way as Apache Cassandra.
The missing clustering key is the timestamp. Apache Cassandra doesn't require that all clustering keys are defined for deletes.
A workaround for that could be to not have the timestamp as a clustering key for CosmosDB. I still think we should have it for Cassandra because it's nice that we don't overwrite when accidentally using same pid/seqnr.
We also have the timebucket, but that can be removed #399
The text was updated successfully, but these errors were encountered: