On Fri, Jan 21, 2011 at 5:14 AM, Anand Somani <meatfor...@gmail.com> wrote:
> Here is what worked for me, I use testNg, and initialize and createschema > in the @BeforeClass for each test > > - In the @AfterClass, I had to drop schema, otherwise I was getting the > same exception. > - After this I started getting port conflict with the second test, so I > added my own version of EmbeddedCass.. class, added a stop which calls a > stop on the cassandradaemon (which from code comments seems to closes the > thrift port) > > How was this clean-up experience, Anand? Shutting down the cassandra daemon and droping and creating schema between tests? Sounds like something that could be time consuming. I am currently firing all-deletes on all my CFs and am looking for more efficient ways to have data cleaned-up between tests. Thanks.
