Ok. So, running the update processor chain *is* the commit process? In answer to Erick's question: my habit, an old and apparently bad one, has been to call a hard commit at the end of each update. My question had to do with allowing soft commits to be controlled by settings in solrconfig.xml, say every 30 seconds or something like that (I really haven't studied such options yet).
I ask this question because I add an additional call to the update processor, which, after running Lucene, the document is then sent outside to an agent network for further processing. I needed to know if the document was already committed by that time. I am inferring from here that the document has been committed after the first step in the update processor chain, even if that's based on a soft commit. Thanks! JackP On Wed, Aug 7, 2013 at 4:20 PM, Jack Krupansky <j...@basetechnology.com> wrote: > Most update processor chains will be configured with the Run Update > processor as the last processor of the chain. That's were the Lucene index > update and optional commit would be done. > > -- Jack Krupansky > > -----Original Message----- From: Jack Park > Sent: Wednesday, August 07, 2013 1:04 PM > To: solr-user@lucene.apache.org > Subject: Question about soft commit and updateRequestProcessorChain > > > If one allows for a soft commit (rather than a hard commit on each > request), when does the updateRequestProcessorChain fire? Does it fire > after the commit? > > Many thanks > Jack
