[jira] [Assigned] (CASSANDRA-10888) Tombstone error warning does not log partition key

["Brett Snyder (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-10888?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Snyder reassigned CASSANDRA-10888:
----------------------------------------

    Assignee: Benjamin Lerer  (was: Brett Snyder)

Attached a patch against 2.2.x ...what you suggested was correct about removing setKey, etc.  The patch will NOT apply to 3.0, but the issue is also not displayed in the 3.0 series as far as I can tell because the code is completely different and the partition key is already logged.

Thanks!

> Tombstone error warning does not log partition key
> --------------------------------------------------
>
>                 Key: CASSANDRA-10888
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10888
>             Project: Cassandra
>          Issue Type: Improvement
>         Environment: DSE 4.8.2
>            Reporter: Ole Pedersen
>            Assignee: Benjamin Lerer
>         Attachments: 10888-2.1.txt, 10888-2.2.txt
>
>
> Log partition key if read fails due to the ERROR threshold on read tombstoned cells.
> Right now I can specify a warning and an error threshold for C* when reading from a partition with many tombstones.
> If the query reads more than the “warning threshold” then C* writes a warning to the log with the partition key.
> But if a query reads more than the “error threshold” then C* aborts the query and writes to the log – but not the partition key, this time. 
> What I am missing is: Could C* also please write the partition key in case of query abort due to tombstones?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)