Hi Anuj, Thanks for the detailed design document. We had a similar requirement recently for our internal 2.1 clusters and we implemented a simple version (no "Separate Configuration for Whitelisted Users" etc…) for sox auditing. As your design is very close to what we implemented, just a few differently named classes, for the most part, I updated our patch for trunk <https://github.com/vinaykumarchella/cassandra/pull/2> and put it out there for reviewing it. We could take an incremental approach, review what we have on the trunk branch of the simple version and then add in some of the more advanced features next. I believe this patch follows the design goals that you put together.
Please review and let me know if you have any questions or concerns about the first iteration. If folks are interested in the 3.x/2.x branches I can put those up on my github as well. @Dinesh, Thanks in advance for your time in reviewing it. Thanks, Vinay Chella Thanks, Vinay Chella On Mon, Feb 26, 2018 at 11:56 PM, Dinesh Joshi < dinesh.jo...@yahoo.com.invalid> wrote: > Hey Anuj, > Thanks for submitting the patch. I am looking at the design. Will comment > on the Jira with my feedback. > Dinesh > > On Monday, February 26, 2018, 4:09:41 AM PST, Anuj Wadehra < > anujw_2...@yahoo.co.in.INVALID> wrote: > > Hi, > Apache Cassandra doesn't provides an auditing feature. As Database > auditing is critical for any production level database like Apache > Cassandra, our team is keen on designing & implementing this feature in > Apache Cassandra. > I have submitted the Design proposal for "Database Auditing" feature under > the JIRA: https://issues.apache.org/jira/browse/CASSANDRA-12151 . Can > some of you please review the proposal and share your feedback? > > > ThanksAnuj > > >
