[
https://issues.apache.org/jira/browse/CASSANDRA-9465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14727353#comment-14727353
]
Carl Yeksigian commented on CASSANDRA-9465:
-------------------------------------------
I've pushed a
[branch|https://github.com/carlyeks/cassandra/tree/ticket/9465/2.2] -- it
changes the TracingAwareExecutor to allow for including other thread local
state to be passed onto the task being run, currently just {{Tracing}} and
{{ClientWarn}}.
This change doesn't address remote warnings, so if the coordinator is not also
the replica, we still won't get the messages. That requires a change to the
internode protocol to add warnings, so it wouldn't be included in 2.2.
> No client warning on tombstone threshold
> ----------------------------------------
>
> Key: CASSANDRA-9465
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9465
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Adam Holmberg
> Assignee: Carl Yeksigian
> Priority: Minor
> Fix For: 2.2.x
>
>
> It appears that a client warning is not coming back for the tombstone
> threshold case. The batch warning works.
> Repro:
> Create a data condition with tombstone_warn_threshold < tombstones <
> tombstone_failure_threshold
> Query the row
> Expected:
> Warning in server log, warning returned to client
> I'm basing this expectation on what I see
> [here|https://github.com/apache/cassandra/blob/68722e7e594d228b4bf14c8cd8cbee19b50835ec/src/java/org/apache/cassandra/db/filter/SliceQueryFilter.java#L235-L247]
> Observed:
> Warning in server log, no warning flag in response message.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
