I really can't comment on Cassandra, but the flight time of transactions is likely to be too slow for updates not to be batched. With a server round-trip in the way, you are looking at hundreds of microseconds at least and you need dozens to thousands of these to add a document to the index.
You also would like a single document addition to be roughly transactional. That is a really hard thing to do for an inverted with any noSQL solution I have heard of. On Sun, Feb 13, 2011 at 9:37 AM, Sean Bigdatafun <sean.bigdata...@gmail.com>wrote: > > Short queries would involve reading and merging several posting vectors. > > In > > that mode, query speeds might be OK, but there isn't a lot of Lucene left > > at > > that point. For updates, speed would only be acceptable if you batch up > a > > lot updates or possibly if you build in a value append function as a > > co-processor. > > > > "speed would only be acceptable if you batch up " -- I understand what you > are talking about here (without batching-up, HBase simply become very > sluggish). Can you comment if Cassandra needs a batch-up mode? (I recall > Twitter said they just keep putting results into Cassandra for its > analytics > application) >
