You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "C. Scott Andreas (JIRA)" <ji...@apache.org> on 2018/05/24 20:25:00 UTC
[jira] [Commented] (CASSANDRA-14467) Add option to sanity check
tombstones on reads/compaction
[ https://issues.apache.org/jira/browse/CASSANDRA-14467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16489734#comment-16489734 ]
C. Scott Andreas commented on CASSANDRA-14467:
----------------------------------------------
Thanks Marcus!
To confirm my understanding, looks like this approach identifies a tombstone as potentially invalid when:
*Cell:*
* A cell's TTL is less than zero;
* Its local deletion time is less than zero;
* Or a TTL is set but its local deletion time is Integer.MAX_VALUE
*Row:*
* Primary key has a TTL less than zero;
* Primary key's local expiration time is less than zero;
* Row's deletion timestamp < 0 (!>=0);
* Or if the column data it contains has invalid deletions (either via complexDeletion validation for range tombstones, or as defined using the Cell criteria above for cells)
Does that summary look correct to you?
> Add option to sanity check tombstones on reads/compaction
> ---------------------------------------------------------
>
> Key: CASSANDRA-14467
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14467
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Priority: Minor
> Fix For: 4.x
>
>
> We should add an option to do a quick sanity check of tombstones on reads + compaction. It should either log the error or throw an exception.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org