: I'm assuming the processCommit method is called for each
: UpdateRequestProcessor chain class when the records are being commited to
: the Lucene index.
Not exactly.
RequestHandlers that want to modify the index do so by asking the SolrCore
for a processor chain (either by name or just get the default), and then
they execute methods on that chain passing in instances of UpdateCommand
objects that model the type of index update they want to perform.
The first element in the chain decides if/when to pass the UpdateCommand
on to subsequent members of the chain, and most processor chains include
a "RunUpdateProcessorFactory" instance, which is responsible for actually
performing the "update" on the UpdateHandler used by the SolrCore.
Which means:
1) there is no garuntee that processCommit is called on every
UpdateRequestProcessor in the chain -- that's entirely dependent on what
comes before RunUpdateProcessorFactory in the chain.
2) RunUpdateProcessorFactory itself is what tells the underlying
IndexWriter to commit (ie: processCommit is not a callback method done
after the underlying commit happens -- you may be comfusing
UpdateRequestProcessor with the SolrEventListener API)
: I'm debugging the processor chain using the debug functionality in the
: dataimport.jsp page, and I have selected verbose and commit as options.
: When I import 10 records,
: the processAddd methods are getting called, but the processCommit methods
: aren't.
...
: I'm using SOLR 1.4
Hmmm... I can confirm the behavior you describe in Solr 1.4.1, but using
Solr 3.5.0 I can see that the processCommit method is definitely getting
called by DIH when using the "Debug Now" button of the DIH console when
the "commit" checkbox is checked (FWIW: I tested using the 'rss' core
of example-DIH/solr and watching the logs for the log messages from
LogUpdateProcessorFactory)
So please consider upgrading -- besides this evident fix, there have been
a *TON* of other bug fixes and other improvements between Solr 1.4 and
Solr 3.5.
-Hoss
