[
https://issues.apache.org/jira/browse/CASSANDRA-14772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625898#comment-16625898
]
Joshua McKenzie commented on CASSANDRA-14772:
---------------------------------------------
Having not looked at the code, is there value in moving the API changes and
defect fixes to their own ticket targeting 4.0 and doing the other parts 4.0.x
(black box refactors, etc)?
I'm mostly coming at this from a "broken windows theory" angle of us having
discipline w/the concept of a code-freeze. Don't want us to get into the habit
of sneaking things in past the date, which then further risks destabilizing the
testing period.
> Refactor audit / full query log
> -------------------------------
>
> Key: CASSANDRA-14772
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14772
> Project: Cassandra
> Issue Type: Bug
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Priority: Major
> Fix For: 4.0
>
>
> I find the audit + full query log code quite hard to follow with some of the
> naming and mixing of concepts, this ticket aims to:
> * move full query log specific code to a separate package
> * do some audit log class renames (I keep reading {{BinLogAuditLogger}} vs
> {{BinAuditLogger}} wrong for example)
> * avoid parsing the CQL queries twice in {{QueryMessage}} when audit log is
> enabled.
> * add a new tool to dump audit logs (ie, let fqltool be full query log
> specific)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
