[
https://issues.apache.org/jira/browse/CASSANDRA-12106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17423540#comment-17423540
]
Sumanth Pasupuleti commented on CASSANDRA-12106:
------------------------------------------------
{quote}I tend to dislike risk (even the minimal risk of differing data types in
memory vs. table and conversion on load); we can document this (including the
CQL to query and convert to human readable) to work around that little
usability friction. wdyt?{quote}
I agree. +1 to documenting the CQL for easy reference. Also, nodetool commands
maybe able to make this easy - we can defer the nodetool discussion to a follow
up ticket like you mentioned.
{quote}the code-paths warn if you're above either the global or per-table
level{quote}
+1 to the improved logging. I still think we can do better in avoiding corner
case cache inconsistency
https://github.com/apache/cassandra/pull/1213/commits/0fb6ae95149a1a6601208cdae4b165835ea10070#r720686050
> Add ability to blocklist / denylist 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
> Components: Legacy/Local Write-Read Paths, Local/Config
> Reporter: Geoffrey Yu
> Assignee: Josh McKenzie
> Priority: Low
> 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 blocklist / denylist
> such partitions so all read and write requests to them are rejected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
