Re: CASSANDRA-14482

2019-03-01 Thread Jonathan Haddad
I plan on doing some more thorough testing, it’s just a matter of finding time. On Fri, Mar 1, 2019 at 7:17 PM Dinesh Joshi wrote: > Thanks for testing this out Jon. Apart from the compression ratio could > you also test the insertion rate and GC? 14482 allows you to use full range > of Zstd

Re: CASSANDRA-14482

2019-03-01 Thread Dinesh Joshi
Thanks for testing this out Jon. Apart from the compression ratio could you also test the insertion rate and GC? 14482 allows you to use full range of Zstd compression levels. Dinesh > On Mar 1, 2019, at 6:41 PM, Jonathan Haddad wrote: > > Hey all, > > I finally got around to doing some

Re: CASSANDRA-14482

2019-03-01 Thread Jonathan Haddad
Hey all, I finally got around to doing some testing. Nothing too crazy, I had it run on my laptop while I did other things around the house. Test 1: Inserting Random Data in a K/V table, 10 million inserts LZ4 compression rate: 0.909857609644112 ZStd: 0.6136099401596449 Test 2: Inserting

Re: Audit logging to tables.

2019-03-01 Thread Jonathan Haddad
Instead of logging to tables, putting a virtual table around the audit / query logs might be an option. Same with the commit log for cdc On Fri, Mar 1, 2019 at 5:25 PM Sagar wrote: > Thanks all for the pointers. Really insightful. > > Subroto I think that’s part of the enterprise version but

Re: Audit logging to tables.

2019-03-01 Thread Sagar
Thanks all for the pointers. Really insightful. Subroto I think that’s part of the enterprise version but yeah even I have seen it. Again not sure of the performance implications. Sagar. On Sat, 2 Mar 2019 at 5:15 AM, Subroto Barua wrote: > Datastax version has an option to store audit info

Re: Audit logging to tables.

2019-03-01 Thread Subroto Barua
Datastax version has an option to store audit info to dse_audit.audit_log table; I do not know the performance impact since I use the file option Subroto > On Mar 1, 2019, at 9:40 AM, Jeremiah D Jordan > wrote: > > AFAIK the Full Query Logging binary format was already made more general in

RE: Looking for common cases in cassandra fit to autoheal

2019-03-01 Thread Kenneth Brotman
Michael is right. It's not the topic of this list. Write me offline and I'll be glad to direct you to some resources with the information you are looking for. Kenneth Brotman -Original Message- From: Michael Shuler [mailto:mshu...@pbandjelly.org] On Behalf Of Michael Shuler Sent:

Re: Looking for common cases in cassandra fit to autoheal

2019-03-01 Thread Dinesh Joshi
Natarajan, it looks like your company is trying to build a monetizable solution around Cassandra. It would be helpful for you to look at the literature around Cassandra and consult with folks who run Cassandra. Perhaps also contribute back learnings to our community so we might benefit from it

Re: Looking for common cases in cassandra fit to autoheal

2019-03-01 Thread Michael Shuler
Your request is not related to the topic of this mailing list, the development of Apache Cassandra. Your question would be better suited for the user@ mailing list. Your question is also quite vague, and you might include some detail or context about what exactly you are looking for. You may also

RE: Looking for common cases in cassandra fit to autoheal

2019-03-01 Thread Sundaramoorthy, Natarajan
Can someone please reply? Thanks     -Original Message- From: Sundaramoorthy, Natarajan [mailto:natarajan_sundaramoor...@optum.com] Sent: Wednesday, February 27, 2019 3:17 PM To: dev@cassandra.apache.org Subject: Looking for common cases in cassandra fit to autoheal Can someone please

Re: Audit logging to tables.

2019-03-01 Thread Jeremiah D Jordan
AFAIK the Full Query Logging binary format was already made more general in order to support using that format for the audit logging. -Jeremiah > On Mar 1, 2019, at 11:38 AM, Joshua McKenzie wrote: > > Is there a world in which a general purpose, side-channel file storage > format for