Re: State of triggers
There wasn't much work done on triggers since they "came out". Basically it was always marked as experimental and never got to a usable production ready state. CDC is going to become a new way of doing things that made you look into triggers. Other than that as Jeff said, I never met or heard about anyone using triggers in production. On Thu, Mar 2, 2017 at 8:41 PM, Jeff Jirsa wrote: > As far as I know, I've never met anyone who wrote and used their own > triggers in production. I imagine the number of people doing so is very > small, regardless of version. > > On Thu, Mar 2, 2017 at 11:04 AM, S G wrote: > > > Hi, > > > > I am not able to find any documentation on the current state of triggers > > being production ready. > > > > The post at > > http://www.datastax.com/dev/blog/whats-new-in-cassandra-2- > > 0-prototype-triggers-support > > says that "The current implementation is experimental, and there is some > > work to do before triggers in Cassandra can be declared final and > > production-ready." > > > > So which version of Cassandra should we expect triggers to be stable > > enough? > > Our requirement is to develop a solution for several Cassandra users all > > running on different versions (they won't upgrade easily) and no one is > > using 3.5+ versions. > > So the smallest Cassandra version which has production ready triggers > would > > be really good to know. > > > > Also any advice on common gotchas with Cassandra triggers would be great > to > > know. > > > > Thanks > > SG > > >
Re: State of triggers
As far as I know, I've never met anyone who wrote and used their own triggers in production. I imagine the number of people doing so is very small, regardless of version. On Thu, Mar 2, 2017 at 11:04 AM, S G wrote: > Hi, > > I am not able to find any documentation on the current state of triggers > being production ready. > > The post at > http://www.datastax.com/dev/blog/whats-new-in-cassandra-2- > 0-prototype-triggers-support > says that "The current implementation is experimental, and there is some > work to do before triggers in Cassandra can be declared final and > production-ready." > > So which version of Cassandra should we expect triggers to be stable > enough? > Our requirement is to develop a solution for several Cassandra users all > running on different versions (they won't upgrade easily) and no one is > using 3.5+ versions. > So the smallest Cassandra version which has production ready triggers would > be really good to know. > > Also any advice on common gotchas with Cassandra triggers would be great to > know. > > Thanks > SG >
Re: State of triggers
+1 On Thu, Mar 2, 2017 at 11:04 AM, S G wrote: > Hi, > > I am not able to find any documentation on the current state of triggers > being production ready. > > The post at > http://www.datastax.com/dev/blog/whats-new-in-cassandra-2- > 0-prototype-triggers-support > says that "The current implementation is experimental, and there is some > work to do before triggers in Cassandra can be declared final and > production-ready." > > So which version of Cassandra should we expect triggers to be stable > enough? > Our requirement is to develop a solution for several Cassandra users all > running on different versions (they won't upgrade easily) and no one is > using 3.5+ versions. > So the smallest Cassandra version which has production ready triggers would > be really good to know. > > Also any advice on common gotchas with Cassandra triggers would be great to > know. > > Thanks > SG >
State of triggers
Hi, I am not able to find any documentation on the current state of triggers being production ready. The post at http://www.datastax.com/dev/blog/whats-new-in-cassandra-2-0-prototype-triggers-support says that "The current implementation is experimental, and there is some work to do before triggers in Cassandra can be declared final and production-ready." So which version of Cassandra should we expect triggers to be stable enough? Our requirement is to develop a solution for several Cassandra users all running on different versions (they won't upgrade easily) and no one is using 3.5+ versions. So the smallest Cassandra version which has production ready triggers would be really good to know. Also any advice on common gotchas with Cassandra triggers would be great to know. Thanks SG
Re: Lots of dtest errors on local machine
Sorry - it was my fault. I introduced a bug and was blinded by the tons of debug output of dtests. 2017-03-01 17:20 GMT+01:00 benjamin roth : > Hi again, > > I wanted to run some dtests (e.g. from materialized_views_test.py) to > check my changes. A while ago, everything worked fine but today I ran into > a lot of errors like this: > https://gist.github.com/brstgt/114d76769d97dc72059f9252330c4142 > > This happened on 2 different machines (macos + linux). > CS Version: 4.0 (trunk of today) > CCM: 2.6.0 > > I deleted and reinstalled all python deps. > I also checked the ccm logs (as long as I was able to access them, because > dtests delete them after the test) > In the attached log, 127.0.0.2 caused. In ccm logs I saw, that the node > was stopped by the test, started again and seemed to boot up again > correctly. > > Running some of these tests against 3.11 worked. > Switching back to trunk/4.0 - ERROR > > Is this a known issue - maybe caused by removed RPC support? Am I maybe > doing sth wrong? >