On Tue, Mar 8, 2011 at 7:33 PM, Buttler, David <buttl...@llnl.gov> wrote:
Has someone implemented a complementary blob storage mechanism, or is this > something still on the roadmap? > Well, yes. :-) > The Lily blob storage looks very interesting, but also tightly integrated > into their CMS > We prefer "data repository" but I catch your drift. We support blob storage inline in the Lily record table, in a separate blob table, and in HDFS. The client API also connects directly to HBase or HDFS for retrieving blobs for reasons of efficiency. > (if the Lily guys are listening: We typically do, but are pretty busy with our 1.0 release. > would you like to reconsider your choice of solr over elastic search? Reconsider: no, but yes, we have 'somewhere along the roadmap' the intention to support ES alongside SOLR. For our enterprise users, SOLR fits the bill quite nicely. When running distributed, you can have heavy index calculation nodes and only the computed index segments are then replicated to slaves, whileas ES requires all nodes to be identical (AFAIU) because indexes are computed locally (Shay: correct me if I'm wrong). > The solr sharding you describe seems a bit painful) > Again, we haven't encountered issues, yet. Resharding is painful, but we provide index mgmt around that. Again, ES support is planned for later this year, but I cannot confirm a hard date yet. Kind regards, -- Steven Noels http://outerthought.org/ Scalable Smart Data Makers of Kauri, Daisy CMS and Lily
