It's not 'mandatory', but it makes no sense to keep it. Even without
autocommit, committing after every doc add is horribly inefficient.
On Oct 25, 2011, at 9:45 AM, darul wrote:
> Well until now I was using SolrJ API to commit() (for each document added...)
> changes but wonder in case of a production deployment it was not a best
> solution to use AutoCommit feature instead.
>
> With AutoCommit parameters, is it mandatory to remove commit() instruction
> called on CommonsHttpSolrServer
>
> try
> {
> getServer().addBean(o);
> getServer().commit(); => to remove ?
> ...}
>
> I just have another questions, I was looking all over the threads but not
> found any solutions yet about how to get a CallbackHandler with all
> documents commited. Is there a way simple way to achieve this ?
>
> Thanks again Erick.
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/questions-about-autocommit-committing-documents-tp1582487p3450739.html
> Sent from the Solr - User mailing list archive at Nabble.com.
- Mark Miller
lucidimagination.com
