You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (Jira)" <ji...@apache.org> on 2019/08/28 13:56:00 UTC
[jira] [Updated] (CASSANDRA-14772) Fix issues in audit / full query
log interactions
[ https://issues.apache.org/jira/browse/CASSANDRA-14772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksey Yeschenko updated CASSANDRA-14772:
------------------------------------------
Reviewers: Aleksey Yeschenko, Per Otterström, Vinay Chella, Aleksey Yeschenko (was: Aleksey Yeschenko, Per Otterström, Vinay Chella)
Aleksey Yeschenko, Per Otterström, Vinay Chella, Aleksey Yeschenko (was: Aleksey Yeschenko, Per Otterström, Vinay Chella)
Status: Review In Progress (was: Patch Available)
> 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
> Components: Legacy/CQL, Legacy/Tools
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Priority: Normal
> 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
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org