[ https://issues.apache.org/jira/browse/CASSANDRA-16725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17389295#comment-17389295 ]
Stefan Miklosovic commented on CASSANDRA-16725: ----------------------------------------------- thanks [~e.dimitrova] for the review, I reflected that already, same PR / branch. The build is here [https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/983/#showFailuresLink] I think that the only thing remaining is to ask what to do with jmx methods as mentioned in my other comment otherwise if you do not have any objections I think we might just ship it as it is. > 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: 5.5h > 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org