> Sorry if this is a naive question but can you explain why you consider > that ElasticSearch isn't a distributed solution for realtime search?
I wasn't referring just to ES, mainly to Katta and Solr. Taking a step back, RT in Lucene should enable immediate consistency making it symmetrical with HBase? Outside of that there are 'containers' for Lucene, some of which are Katta, Solr, and ES. My opinion is that they each have drawbacks compared to HBase as a Lucene container. If one is running HBase in production, then adding a Lucene index on that data shouldn't add more complexity to operating HBase. And so if one's primary data store is HBase, my opinion is that one'd be adding significant additional complexity be adding 'another' cluster server system alongside. Especially given the requirements and symmetrical (eg, write-once, immediate consistency) nature of HBase and Lucene. Once everything is polished I think it'll be a nice solution that can replace many MySQL depoyments for realtime data access. One that'd offer even more types of queries and scalability than MySQL. If the user wishes to perform joins they can use Hive?
