[
https://issues.apache.org/jira/browse/CASSANDRA-14772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625885#comment-16625885
]
Aleksey Yeschenko commented on CASSANDRA-14772:
-----------------------------------------------
It's a follow-up to a feature introduced in an unreleased version (4.0). There
are some issues with it that need to be addressed, including a performance
regression in FQL that makes it less usable than it should be.
So 4.0 is a fitting fixver for at least part of this JIRA, yes. Additionally,
the API will be harder to change post-stable 4.0, but arguably it needs to. So
again, 4.0 is the correct fixver here.
> 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.x
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
