This could be caused by HTTP caching. Solr's example solrconfig.xml
comes with HTTP caching turned on, and this causes lots of beginners
to have problems. The code to turn it off is commented in
solrconfig.xml. Notice that the default is to have caching on, so to
turn it off you have to have the
Hi all,
I've been working with Solr for a few weeks and have gotten SolrJ
to connect to it, index, search documents.
However I am having an issue when a document is committed.
When a document is committed it does not show in the search results if I do
a *:* search,
but if I search for it with
The underlying IndexReader must be reopened. If you're
searching for a document with a searcher that was opened
before the document was indexed, it won't show up on the
search results.
I'm guessing that your statement that when you search
for it with some test is coincidence, but that's just a
Thanks for the reply.
Here is another thread I found similar to this
http://www.mail-archive.com/solr-user@lucene.apache.org/msg28236.html
From what I understand the IndexReaders get reopened after a commit.
Regards,
Indika
On 2 May 2010 00:29, Erick Erickson erickerick...@gmail.com wrote:
Sunny Bassan wrote:
I have implemented the embedded SOLR approach for indexing of database
records. I am indexing approximately 10 millions records, querying and
indexing 20,000 records at a time. Each record is added to the
updateHandler via the updateHandler.addDoc() function once all 20,000
I have implemented the embedded SOLR approach for indexing of database
records. I am indexing approximately 10 millions records, querying and
indexing 20,000 records at a time. Each record is added to the
updateHandler via the updateHandler.addDoc() function once all 20,000
records have been added
