Agreed with Dinesh and Josh. I would *never* put the audit log back in
Cassandra.
This is extendable, Sagar, so you're free to do as you want, but I'm very
opposed to putting a ticking time bomb in Cassandra proper.
Jon
On Thu, Feb 28, 2019 at 8:38 AM Dinesh Joshi
wrote:
> I strongly echo Jo
I strongly echo Josh’s sentiment. Imagine losing audit entries because C* is
overloaded? It’s fine if you don’t care about losing audit entries.
Dinesh
> On Feb 28, 2019, at 6:41 AM, Joshua McKenzie wrote:
>
> One of the things we've run into historically, on a *lot* of axes, is that
> "just p
One of the things we've run into historically, on a *lot* of axes, is that
"just put it in C*" for various functionality looks great from a user and
usability perspective, and proves to be something of a nightmare from an
admin / cluster behavior perspective.
i.e. - cluster suffering so you're wri
Thanks all for the pointers.
@Joseph,
I have gone through the links shared by you. Also, I have been looking at
the code base.
I understand the fact that pushing the logs to ES or Solr is a lot easier
to do. Having said that, the only reason I thought having something like
this might help is, if
