There's no official roadmap as far as I know, It's mostly about cleaning up code, adding tests, fixing bits and adding a bare minimum of user friendlyness. There is a thread in the apache mailing list archives called "Roadmap" with some more details.
You can get an overview of the issues assigned to 0.3.0 over here, no guarantee they'll all make it into that release though: https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=12310865&fixfor=12313861&sorter/field=priority&sorter/order=DESC /Johan Jonas Bonér wrote: > Thanks for the answers. > > Btw, is the CQL in usable state? If not, any plans? > What about the CLI interface? > Is there an open roadmap on what you are focusing for the next > release, when it is planned for, etc.? > > Thanks, Jonas. > > 2009/5/1 Jonathan Ellis <[email protected]>: >> On Fri, May 1, 2009 at 5:59 AM, Jonas Bonér <[email protected]> wrote: >>> Hi there. >>> >>> First, should I use this ML or the google forum? >> This one. >> >>> * What does the new timestamp arg in >>> public boolean remove(String tablename, String key, String >>> columnFamily_column, long timestamp, boolean block) >>> specify? >> It's compared against the timestamp in insert, to make sure remove >> doesn't get applied to newer data than it was intended to. >> >>> * Any reason for making ctor in CassandraServer protected? I am >>> embedding Cassandra and now I have to use reflection to create the >>> instance. No big deal, just checking why? >> No particular reason I know of. We can make that public. >> >>> * I get this exception when invoking batch_update (in the previous >>> release, haven't tried with the latest trunk yet): >> Yeah, that's a long-standing bug. I have a patch to fix it here >> https://issues.apache.org/jira/browse/CASSANDRA-120 that is waiting >> for review. >> >> -Jonathan >> > > >
