re: batching every hour. It Depends (tm). You haven't told us how many documents change every hour. But Solr will easily handle quite a few.
If you have a bunch of documents to add, it's definitely a Bad Idea to commit each one. I'd rely on autocommit properties or, if you're using SolrJ, the commitWithin parameter. Best, Erick On Sat, Mar 1, 2014 at 1:50 PM, jurio <[email protected]> wrote: > Thank you for your answer Erick. > > Yes, i index and then commit the document when there are any document > modification. > > At the begining I prefered to index document when the document change > because : > - I want up to date documents. > - It's better for performance to not index all documents all times. > > Using batch can be a good idea because : > - has you said it less work because i can accumulate the index and commit at > the end. > - If indexed documents are lost or something else i can easily reconstruct > the index > - I decouple the job for indexing and for my changed documents (update, > remove...) > - If there is failure by indexing at a time (server dies...) i can't reindex > my document > > If i decide to use batch to index all documents every one hour, can i be > worry about performance ? Time to accomplish the indexing ?How many simple > document [with about 10 simple fields] solr can index per minute ? > > > > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Best-strategy-to-index-document-with-Solr-tp4120614p4120646.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]
