On 12/3/2014 6:10 AM, Bill Drake wrote: > I have an existing application that includes Lucene code. I want to add > high availability. From what I have read SolrCloud looks like an effective > approach. My problem is that there is a lot of Lucene code; out of 100+ > java files in the application more than 20 of them are focused on Lucene > code. Refactoring this much code seems very risky. > > My thought was to migrate the index from Lucene 35 to Solr/Lucene 4.10 then > after making sure everything still works I would add in the HA. I looked at > solrj with the hope that it would look like Lucene but it did not look like > it would simplify the transition. > > So the question is can I leave most of the existing Lucene code and just > make small changes to get the benefit of HA from SolrCloud. Is there a > better approach?
Does the Lucene code have a "client" layer on top of it, or does the application use Lucene directly? If it's the latter, you have a lot of work to do, but if there's a client layer, you can hopefully just refactor the code that uses the client layer a little to use SolrJ. Solr hides almost all of the Lucene complexity in its server-side configuration, SolrJ is a simple client to access Solr. Thanks, Shawn
