[
https://issues.apache.org/jira/browse/CASSANDRA-16725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17399871#comment-17399871
]
Ekaterina Dimitrova commented on CASSANDRA-16725:
-------------------------------------------------
I just tested that it fails for me locally on 3.11, 4.0, trunk. While it is
definitely caused by this patch, I am pretty sure it was not failing last
summer as I remember I was looking into changes there back then. So it seems
now we have classic flaky test... I will open a separate ticket
> Implement nodetool getauditlog command
> --------------------------------------
>
> Key: CASSANDRA-16725
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16725
> Project: Cassandra
> Issue Type: New Feature
> Components: Tool/auditlogging
> Reporter: Stefan Miklosovic
> Assignee: Stefan Miklosovic
> Priority: Normal
> Fix For: 4.1
>
> Time Spent: 13h 40m
> Remaining Estimate: 0h
>
> There is getfullquerylog already, there is not any reason why getauditlog
> should not be there too. A user can not retrieve runtime configuration of
> Audit log, it might be only enabled and disabled via jmx but its state can
> not be queried in runtime.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
