Hi Marcel, Yes I ran another query straight after and the execution time drops from 37000ms to 16ms! So the delay when the query is first ran is due to text extraction and indexing having to complete?
This leads to another question. Page 59 of Lucene In Action states: "Any number of read-only operations may be executed while an index is being modified. For example, users can search an index while it's being optimized or while new documents are being added to the index, updated, or deleted from the index." It seems that this behaviour of Lucene is not the situation when Jackrabbit integrates with Lucene. Is there a reason for the index not being readable while the extraction / indexing takes place? Cheers, Thomas -- View this message in context: http://www.nabble.com/Is-doc-addition-indexing-synchronous-or-asynchronous--t1400122.html#a3838472 Sent from the Jackrabbit - Dev forum at Nabble.com.
