I think i will invest the time launching cassandra in a forked forground process, maybe building the yaml dynamically.
On Friday, December 27, 2013, Nate McCall <n...@thelastpickle.com> wrote: > I've also moved on to container-based (using Vagrant+docker) setup for doing automated integration stuff. This is more difficult to configure for build systems like Jenkins, but it can be done and once completed the benefits are substantial - as Joe notes, the most immediate is the removal of variance between different environments. > However, for in process testing with Maven or similar, the Usergrid project [0] probably has the most functionally advanced test architecture [1]. Do understand that it took us a very long time to get there and involves some fairly tight integration with JUnit and (to a lesser degree) maven. > The UG plumbing is purpose built towards a specific data model so it's not something that can be just dropped in, but it can be pulled apart in a straight forward way (provided you understand JUnit - which is not really trivial) and generalized pretty easily. It's all ASF-licensed, so take what you need if you find it useful. > [0] https://usergrid.incubator.apache.org/ > [1] https://github.com/usergrid/usergrid/blob/master/stack/test-utils/src/main/java/org/usergrid/cassandra/CassandraResource.java > > On Wed, Dec 25, 2013 at 2:42 PM, Joe Stein <crypt...@gmail.com> wrote: > > I have been using vagrant (e.g. https://github.com/stealthly/scala-cassandra/ ) which is 100% reproducible across devs and test systems (prod in some cases). Also have a Docker setup too https://github.com/pegasussolutions/docker-cassandra . I have been doing this more and more with clients to better mimic production before production and smoothing the release process from development. I also use packer (scripts released soon) to build images too ( http://packer.io) > Love vagrant, packer and docker!!! Apache Mesos too :) > > > /******************************************* > Joe Stein > Founder, Principal Consultant > Big Data Open Source Security LLC > http://www.stealth.ly > Twitter: @allthingshadoop > ********************************************/ > > On Dec 25, 2013, at 3:28 PM, horschi <hors...@gmail.com> wrote: > > Hi Ed, > > my opinion on unit testing with C* is: Use the real database, not any embedded crap :-) > > All you need are fast truncates, by which I mean: > JVM_OPTS="$JVM_OPTS -Dcassandra.unsafesystem=true" > and > auto_snapshot: false > > This setup works really nice for me (C* 1.1 and 1.2, have not tested 2.0 yet). > > Imho this setup is better for multiple reasons: > - No extra classpath issues > - Faster: Running JUnits and C* in one JVM would require a really large heap (for me at least). > - Faster: No Cassandra startup everytime I run my tests. > > The only downside is that developers must change the properties in their configs. > > cheers, > Christian > > > > On Tue, Dec 24, 2013 at 9:31 PM, Edward Capriolo <edlinuxg...@gmail.com> wrote: > > I am not sure there how many people have been around developing Cassandra for as long as I have, but the state of all the client libraries and the cassandra server is WORD_I_DONT_WANT_TO_SAY. > Here is an example of something I am seeing: > ERROR 14:59:45,845 Exception in thread Thread[Thrift:5,5,main] > java.lang.AbstractMethodError: org.apache.thrift.ProcessFunction.isOneway()Z > at org.apache.thrift.ProcessFunction.process(ProcessFunction.java:51) > at org.apache.thrift.TBaseProcessor.process(TBaseProcessor.java:39) > at org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run(CustomTThreadPoolServer.java:194) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > DEBUG 14:59:51,654 retryPolicy for schema_triggers is 0.99 > In short: If you are new to cassandra and only using the newest client I am sure everything is peachy for you. > For people that have been using Cassandra for a while it is harder to "jump ship" when something better comes along. You need sometimes to support both hector and astyanax, it happens. > For a while I have been using hector. Even not to use hector as an API, but the one nice thing I got from hector was a simple EmbeddedServer that would clean up after itself. Hector seems badly broken at the moment. I have no idea how the current versions track with anything out there in the cassandra world. > For a while I played with https://github.com/Netflix/astyanax, which has it's own version and schemes and dependent libraries. (astyanax has some packaging error that forces me into maven3 > > -- > ----------------- > Nate McCall > Austin, TX > @zznate > > Co-Founder & Sr. Technical Consultant > Apache Cassandra Consulting > http://www.thelastpickle.com -- Sorry this was sent from mobile. Will do less grammar and spell check than usual.
