[
https://issues.apache.org/jira/browse/CASSANDRA-12106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15386515#comment-15386515
]
sankalp kohli commented on CASSANDRA-12106:
-------------------------------------------
Regarding fixing the partitions after it is blocked, many times we want to just
delete the CQL partition by inserting a row tombstone but deciding that
requires app teams to be involved which takes time. You cannot have an outage
till it is decided what to you with this CQL partition.
We can argue that it could be caught during testing of the app but in real
world things happen more often in prod when you run at large scale.
> Add ability to blacklist a CQL partition so all requests are ignored
> --------------------------------------------------------------------
>
> Key: CASSANDRA-12106
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12106
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Geoffrey Yu
> Assignee: Geoffrey Yu
> Priority: Minor
> Fix For: 4.x
>
> Attachments: 12106-trunk.txt
>
>
> Sometimes reads/writes to a given partition may cause problems due to the
> data present. It would be useful to have a manual way to blacklist such
> partitions so all read and write requests to them are rejected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
