[
https://issues.apache.org/jira/browse/CASSANDRA-15988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17165937#comment-17165937
]
Jonathan Shook commented on CASSANDRA-15988:
--------------------------------------------
My take on this:
I think that it is reasonable to show the user whether FQL is enabled or not as
the first item.
Additionally, the configuration of FQL should be dumped to stdout in the same
formatting convention of other nodetool get... commands.
In terms of whether it goes into 4.0 or 4.1, I think it is obviously missing
functionality. Not being able to query the state of the service without
changing it is a problem. 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. As manual as this sounds, many
teams still do this type of ops work and need visibility to the operational
state of the system.
> 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]
