commits only operate on the documents that have been added since the last commit, so that's handled.
If you are using SolrJ, I'd just use the commitWithin parameter and forget about it :)... Best, Erick On Sat, Mar 1, 2014 at 2:08 PM, jurio <[email protected]> wrote: > There are about 200 changes per hour. > > You are right, if I decide to index document after a document modification i > can use property autocommit. > Im using spring data solr to request solr and i think this api is using > SolrJ. > > However if i decide to index with a batch i will only commit at the end of > the batch. > Is there a way to say at solr to only index and commit the changed documents > and not ALL documents ? > > > > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Best-strategy-to-index-document-with-Solr-tp4120614p4120651.html > Sent from the Lucene - Java Developer mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
