[
https://issues.apache.org/jira/browse/CASSANDRA-15819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17110743#comment-17110743
]
David Capwell commented on CASSANDRA-15819:
-------------------------------------------
Its possible the defaults for the cluster are set to false, so absence of
--blocking would be non-blocking, but in the cases where the configs are true
and you should still be able to mark non-blocking.
> nodetool enablefullquerylog doesn't allow caller to make non-blocking
> ---------------------------------------------------------------------
>
> Key: CASSANDRA-15819
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15819
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/nodetool
> Reporter: David Capwell
> Priority: Normal
> Fix For: 4.0-beta
>
>
> {code}
> $ ./bin/nodetool enablefullquerylog --path /tmp/deleteme --blocking false
> Picked up _JAVA_OPTIONS: -Djava.net.preferIPv4Stack=true
> nodetool: Found unexpected parameters: [false]
> See 'nodetool help' or 'nodetool help <command>'.
> {code}
> The root cause is boolean is special cased in airlift, so any time —blocking
> is set it gets turned on.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
