e Run Update is usually the last or next to last
> (like
> > if you use the Log Update processor) processor in the chain. IFF you
> > requested commit, soft or hard, on your update command, the commit will
> > occur on the Run Update processor step of the chain.
>
e chain. IFF you
> requested commit, soft or hard, on your update command, the commit will
> occur on the Run Update processor step of the chain.
>
>
>
>
> -- Jack Krupansky
> -Original Message- From: Jack Park
> Sent: Wednesday, August 07, 2013 7:41 PM
> To: solr-us
-- Jack Krupansky
-Original Message-
From: Jack Park
Sent: Wednesday, August 07, 2013 7:41 PM
To: solr-user@lucene.apache.org
Subject: Re: Question about soft commit and updateRequestProcessorChain
Ok. So, running the update processor chain *is* the commit process?
In answer to Erick's q
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
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: s
How are you allowing for a soft commit? IOW how are you triggering it?
And what do you speculate the updateRequestProcessorChain has to do with
soft commit?
Best
Erick
On Wed, Aug 7, 2013 at 1:04 PM, Jack Park wrote:
> If one allows for a soft commit (rather than a hard commit on each
> reque
