[
https://issues.apache.org/jira/browse/CASSANDRA-16725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17400898#comment-17400898
]
Michael Semb Wever commented on CASSANDRA-16725:
------------------------------------------------
bq. I think there is this "policy" that if one is a committer, all it takes is
another committer to review, 2 are necessary if the original author is not a
committer.
If reviewers have become involved, always try to keep them included and take
some patience for them to wrap up with a formal +1 on the ticket. This is
important to create a warm and inclusive culture here. Ideally reviewers should
remove themselves from the list if they see that they won't be returning to
provide such a +1.
I am listening and following the conversations, and I promise you won't wait
long for me once all remaining questions have been ironed out. The more +1s you
get the better!
> 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: 14h 50m
> 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]
