http://www.datastax.com/support-forums/topic/re-indexing-partial-fields-in-dse-20 Software, Support, and Training for Apache Cassandra en-US Sun, 19 May 2013 14:36:36 +0000 http://bbpress.org/?v=1.0.3 q http://www.datastax.com/support-forums/search.php http://www.datastax.com/support-forums/topic/re-indexing-partial-fields-in-dse-20#post-2039 Tue, 05 Jun 2012 21:18:13 +0000 Anonymous 2039@http://www.datastax.com/support-forums/ <p>&gt; a) How do we keep lucene indexes and CFs in sync? Will index write be attempted first and after that CFs get updated? If CF writes fail, do we rely on commitlog to replay the mutations?</p> <p>The index is in RAM until it is flushed, however the commit log guarantees that data is not lost.</p> <p>&gt; b) Will read-repair work even for native solr queries also?. If we read/write at QUORUM, are we guaranteed to see the correct results returning from nodes?</p> <p>DSE supports writes at quorum.</p> <p>&gt; c) Also we faced a power-cut scenario some time back and corrupted many of our indexes in hadoop. I guess enterprise search is also vulnerable to such issues. In those cases, will a simple re-build of indexes suffice to restore the data?</p> <p>Lucene is generally pretty good in regards to handling things like power outages. With DSE the advantage over regular Solr is the index can be completely rebuilt from the data stored in Cassandra (which as a side notes is also compressed, something Solr / Lucene do not offer). </p> http://www.datastax.com/support-forums/topic/re-indexing-partial-fields-in-dse-20#post-2003 Tue, 29 May 2012 05:27:20 +0000 Anonymous 2003@http://www.datastax.com/support-forums/ <p>Thanks Jake.<br /> Right now, we have built a proprietary distributed search over hadoop using native lucene and are looking for alternatives.</p> <p>I have a few more questions on this architecture</p> <p>a) How do we keep lucene indexes and CFs in sync? Will index write be attempted first and after that CFs get updated? If CF writes fail, do we rely on commitlog to replay the mutations?</p> <p>b) Will read-repair work even for native solr queries also?. If we read/write at QUORUM, are we guaranteed to see the correct results returning from nodes?</p> <p>c) Also we faced a power-cut scenario some time back and corrupted many of our indexes in hadoop. I guess enterprise search is also vulnerable to such issues. In those cases, will a simple re-build of indexes suffice to restore the data?</p> <p>Regards,<br /> Ravi </p> http://www.datastax.com/support-forums/topic/re-indexing-partial-fields-in-dse-20#post-2002 Tue, 29 May 2012 02:39:08 +0000 tjake 2002@http://www.datastax.com/support-forums/ <p>That is correct. Since we hold all the fields in Cassandra we can rebuild the document internally. Please note, to get this behavior using the solr apis you must pass a extra http param. see ,</p> <p><a href="http://www.datastax.com/docs/datastax_enterprise2.0/search/dse_search_cluster#updating-individual-fields-in-a-solr-document" rel="nofollow">http://www.datastax.com/docs/datastax_enterprise2.0/search/dse_search_cluster#updating-individual-fields-in-a-solr-document</a> </p> http://www.datastax.com/support-forums/topic/re-indexing-partial-fields-in-dse-20#post-2001 Mon, 28 May 2012 14:43:40 +0000 Anonymous 2001@http://www.datastax.com/support-forums/ <p>We are evaluating DSE 2.0 for it's ability to re-index fields individually. Our application has lot of update-able fields. We currently store all these fields in the index itself.</p> <p>I am curious as to how DSE 2.0 handles partial updates for fields? Even though it looks like the request updates a single field, under-the-hood will the entire document be read from cassandra and then delete/add to lucene performed?</p> <p>Is my understanding correct or is there some finer details I am missing</p> <p>Regards,<br /> Ravi </p>