[
https://issues.apache.org/jira/browse/CASSANDRA-15988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17165974#comment-17165974
]
David Capwell commented on CASSANDRA-15988:
-------------------------------------------
bq. I think that it is reasonable to show the user whether FQL is enabled or
not as the first item.
we have enable/disable/reset but don't have an "get" version; agree this should
be added.
bq. In terms of whether it goes into 4.0 or 4.1, I think it is obviously
missing functionality
it does not break any API, it does not increase the testing scope, and comes as
low risk; personally I am in favor of 4.0.
bq. Not being able to query the state of the service without changing it is a
problem.
yeah... I hear too much "just take a heap dump"... visibility really should be
part of the features requirements....
bq. Consider a scenario where multiple users are managing a system together and
need to double check the state of things before proceeding to the next step in
their process
A lot of automation does this as well, this isn't just for manual users but
also benefits automation.
> Add nodetool getfullquerylog
> -----------------------------
>
> Key: CASSANDRA-15988
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15988
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Ekaterina Dimitrova
> Priority: Normal
>
> This ticket is raised based on CASSANDRA-15791 and valuable feedback provided
> by [~jshook].
> There are two outstanding questions:
> * forming the exact shape of such a command and how it can benefit the
> users; to be discussed in detail in this ticket
> * Is this a thing we as a project can add to 4.0 beta or it should be
> considered in 4.1 for example
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
