[
https://issues.apache.org/jira/browse/CASSANDRA-19552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18004163#comment-18004163
]
Brandon Williams commented on CASSANDRA-19552:
----------------------------------------------
> It just seems like unnecessary step towards the end goal which is CQL.
The end goal is CQL but there is almost certainly some transition period, and
it is in that period where I want to avoid the worst case of needing to mix and
match both. Also if we are going to put this ticket in 4.1 and not in 5.0 then
that is sending the message that CQL is all you should use, and I'm not sure we
should do that outside of a major, nor am I certain we are ready for it.
> Nodetool to get/set guardrails configurations
> ---------------------------------------------
>
> Key: CASSANDRA-19552
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19552
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Feature/Guardrails
> Reporter: Yuqi Yan
> Assignee: Yuqi Yan
> Priority: Normal
> Fix For: 4.1.x
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently guardrails are only configurable through JMX / cassandra.yaml
> This provides a nodetool command to interact with all the getters/setters for
> guardrails.
>
> 4.1 PR: [https://github.com/apache/cassandra/pull/3243]
> trunk PR: [https://github.com/apache/cassandra/pull/3244]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
