Haven't tried this but: 1) I think SOLR 4 supports on-the-fly core attach/detach/select. Can somebody confirm this? 2) If 1) is true, run everything as two cores. 3) One core is live in production 4) Second core is detached from SOLR and attached to something like SolrJ, which I believe can index without going over network 5) Once SolrJ finished bulk import indexing, switch the cores around
Or if you are not live, just use SolrJ to run the index and then attached finished core to SOLR. Regards, Alex. Personal blog: http://blog.outerthoughts.com/ LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch - Time is the quality of nature that keeps events from happening all at once. Lately, it doesn't seem to be working. (Anonymous - via GTD book) On Fri, Jul 27, 2012 at 9:55 AM, Sohail Aboobaker <sabooba...@gmail.com> wrote: > Hi, > > We have created a search service which is responsible for providing > interface between Solr and rest of our application. It basically takes one > document at a time and updates or adds it to appropriate index. > > Now, in application, we have processes, that add products (our document are > based on products) in bulk using a data bulk load process. At this point, > we use the same search service to add the documents in a loop. These can be > up to 20,000 documents in one load. > > In a recent solr user discussion, it seems like this is a no-no strategy > with red flags all around it. > > What are other alternatives? > > Thanks, > > Regards, > Sohail Aboobaker.
