3.9 falls under the Tick Tock release cycle, which is almost completely untested in production by experienced operators. In the cases where it has been tested, there have been numerous bugs found which I (and I think most people on this list) consider to be show stoppers. Additionally, the Tick Tock release cycle puts the operator in the uncomfortable position of having to decide between upgrading to a new version with new features (probably new bugs) or back porting bug fixes from future versions themselves. There will never be a 3.9.1 release which fixes bugs in 3.9 without adding new features.
https://github.com/apache/cassandra/blob/trunk/NEWS.txt For new projects I recommend starting with the recently released 3.0.9. Assuming the project changes it's policy on releases (all signs point to yes), then by the time 4.0 rolls out a lot of the features which have been released in the 3.x series will have matured a bit, so it's very possible 4.0 will stabilize faster than the usual 6 months it takes for a major release. All that said, there's nothing wrong with doing compatibility & smoke tests against the latest 3.x release as well as 3.0 and reporting bugs back to the Apache Cassandra JIRA, I'm sure it would be greatly appreciated. https://issues.apache.org/jira/secure/Dashboard.jspa Jon On Thu, Oct 6, 2016 at 5:35 PM Ali Akhtar <ali.rac...@gmail.com> wrote: > That looks great Andrew, but it doesn't seem to have been committed to for > 5 months. Is anyone still using cassandra-unit , does it work with latest > cassandra versions (e.g 3.9)? > > On Fri, Oct 7, 2016 at 5:33 AM, Andrew Tolbert < > andrew.tolb...@datastax.com> wrote: > > Hi Ali, > > cassandra-unit <https://github.com/jsevellec/cassandra-unit> might be > what you are looking for. It allows you to run an embedded cassandra > instance along side your tests and has some nice integration with JUnit. > > Thanks, > Andy > > On Thu, Oct 6, 2016 at 7:13 PM Ali Akhtar <ali.rac...@gmail.com> wrote: > > Ok, but that's not what this question is about. > > I'm looking for a way to run an embedded cassandra instance which is > created & destroyed during tests and which doesn't persist any state > outside the tests. > > > On Fri, Oct 7, 2016 at 5:10 AM, Kant Kodali <k...@peernova.com> wrote: > > you dont need to look for cassandra java api to start/stop instance. you > just need to write a shell script or python or java or any language to > execute shell commands! > > > > On Thu, Oct 6, 2016 4:57 PM, Ali Akhtar ali.rac...@gmail.com wrote: > > Okay.. but how would I start this instance? Is there a java api to > programmatically start / destroy an instance during tests? > > On Fri, Oct 7, 2016 at 4:56 AM, Kant Kodali <k...@peernova.com> wrote: > > sure as long as that isolated instance is treated as separate cluster you > shouldn't run into any problems. > > > > On Thu, Oct 6, 2016 4:08 PM, Ali Akhtar ali.rac...@gmail.com wrote: > > Is it possible to create an isolated cassandra instance which is run > during integration tests and it disappears after tests have finished > running? Then its recreated the next time tests run (perhaps being > populated with test data). > > I'm using Java. > > > > > >
