> On Feb 27, 2019, at 10:41 AM, Joseph Lynch <joe.e.ly...@gmail.com> wrote:
>
> Vinay can confirm, but as far as I am aware we have no current plans to
> implement audit logging to a table directly, but the implementation is
> fully pluggable (like compaction, compression, etc ...). Check out the blog
> post [1] and documentation [2] Vinay wrote for more details, but the short
+1. I am still curious as to why you'd want to store audit log entries back in
Cassandra? Depending on the scale it can generate a lot of load and I think
you'd end up in an infinite loop because as you're inserting the audit log
entry you'll generate a new one and so on unless you black list audits to that
table / keyspace.
Ideally you'd insert this data into ElasticSearch / Solr or some other place
that can be then used for analytics or search.
Dinesh
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org