RE: Cassandra Mutation object decoding

I worked on a custom PerRowSecondaryIndex to synchronize data to another system and there was no way to know the difference between an insert and an update at this level (I'm using Cassandra 2.2). The solution for me was simply to us an upsert operation in the target system. There is also the Q

Re: Cassandra Mutation object decoding

> > My goal is to reconstruct the CQL operation from the Mutation object. > So that I can trigger the same action on another NoSQL target like MongoDB. > There are different way of keeping your 2 database in sync. Unfortunatly, they all have some trade offs (as always ;-)) 1. If you have cont

Re: data not replicated on new node

On Tue, Nov 22, 2016 at 5:23 PM, Bertrand Brelier < bertrand.brel...@gmail.com> wrote: > Hello Shalom. > > No I really went from 3.1.1 to 3.0.9 . > So you've just installed the 3.0.9 version and re-started with it? I wonder if it's really supported? Regards, -- Alex

Re: data not replicated on new node

Not sure if it's really related, but we experienced something similar last friday. I summarized it in the following Issue: https://issues.apache.org/jira/browse/CASSANDRA-12947 Best, Malte 2016-11-23 10:21 GMT+01:00 Oleksandr Shulgin : > On Tue, Nov 22, 2016 at 5:23 PM, Bertrand Brelier < > ber

Wiki Contributor

Hi, Could I please be added as a Wiki Contributor Username: Thomas Brown Thank you! -- *Thomas Brown* *Digital Marketing Associate * m: +61427864972 MANAGED. SUPPORT.

STCS in L0 behaviour

Hi everyone, TL;DR Should LCS be changed to always prefer an STCS compaction in L0 if it's falling behind? Assuming that STCS in L0 is enabled. Currently LCS seems to check if there is a possible L0->L1 compaction before checking if it's falling behind, which in our case used between 15-30% of

Re: STCS in L0 behaviour

Without yet reading the code, what you describe sounds like a reasonable optimization / fix, suitable for 3.0+ (probably not 2.2, definitely not 2.1) -- Jeff Jirsa > On Nov 23, 2016, at 7:52 AM, Marcus Olsson wrote: > > Hi everyone, > > TL;DR > Should LCS be changed to always prefer an STCS

Re: STCS in L0 behaviour

What you’re describing seems very close to what’s discussed in   https://issues.apache.org/jira/browse/CASSANDRA-10979 - worth reading that ticket a bit. There does seem to be a check for STCS in L0 before it tries higher levels: https://github.com/apache/cassandra/blob/cassandra-2.2/src/ja

Re: Wiki Contributor

try now On 11/22/2016 06:38 PM, Thomas Brown wrote: Hi, Could I please be added as a Wiki Contributor Username: Thomas Brown Thank you!

FOSDEM 2017 HPC, Bigdata and Data Science DevRoom CFP is closing soon

Hi! apologies for the extra wide distribution (this exhausts my once a year ASF mail-to-all-bigdata-projects quota ;-)) but I wanted to suggest that all of you should consider submitting talks to FOSDEM 2017 HPC, Bigdata and Data Science DevRoom: https://hpc-bigdata-fosdem17.github.io/ It was

Re: Cassandra Mutation object decoding

I must say that it is really encouraging to get your thoughts. Thanks a ton Benjamin, Jacques-Henri, Jordan Nate and Chris. I do not have access on the client side where the CQL is executed. One of my requirements is that my app should not to affect the performance of the cassandra cluster or have

Re: Cassandra Mutation object decoding

> I must say that it is really encouraging to get your thoughts. > Thanks a ton Benjamin, Jacques-Henri, Jordan Nate and Chris. > > I do not have access on the client side where the CQL is executed. QueryHandler (I called it QueryProcessor incorrectly in my initial reply) is server side: https://g

Re: Cassandra Mutation object decoding

Hi Nate, Thank you. I can give it a try. Any examples you can point me to using QueryProcessor to read operations from the CommitLogs? Best regards, Sanal On Thu, Nov 24, 2016 at 1:22 PM, Nate McCall wrote: > > I must say that it is really encouraging to get your thoughts. > > Thanks a ton Be