[ https://issues.apache.org/jira/browse/CASSANDRA-14772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16626327#comment-16626327 ]
Benedict commented on CASSANDRA-14772: -------------------------------------- Also, FWIW, I'm completely in favour of clarifying further for future releases; perhaps having stricter, well defined stages of freeze, culminating in a total code freeze. If we had this, there probably wouldn't have been this confusion (and I think there's been a lot of that) This release cycle is a bit of an experiment IMO, and we should definitely iterate on it for next time. Let's collect our observations and opinions for how we can improve it, and revisit as a community once we have a complete picture. > Fix issues in audit / full query log interactions > ------------------------------------------------- > > 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 > > > There are some problems with the audit + full query log code that need to be > resolved before 4.0 is released: > * Fix performance regression in FQL that makes it less usable than it should > be. > * 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). fqltool crashes when pointed to them. -- 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