@lucene.apache.org
Subject: Re: Combination of EmbeddedSolrServer and CommonHttpSolrServer
On Wed, Mar 11, 2009 at 6:37 PM, Kulkarni, Ajit Kamalakar
ajkulka...@ptc.com wrote:
If we index the documents using CommonsHttpSolrServer and search using
the same, we get the updated results
-Original Message-
From: Ryan McKinley [mailto:ryan...@gmail.com]
Sent: Monday, February 09, 2009 9:23 PM
To: solr-user@lucene.apache.org
Subject: Re: Combination of EmbeddedSolrServer and CommonHttpSolrServer
Keep in mind that the way lucene/solr work is that the results
On Wed, Mar 11, 2009 at 6:37 PM, Kulkarni, Ajit Kamalakar
ajkulka...@ptc.com wrote:
If we index the documents using CommonsHttpSolrServer and search using
the same, we get the updated results
That means we can search the latest added document as well even if it is
not committed to the file
Hi,
Has anybody tried the combination of EmbeddedSolrServer only for
indexing and CommonHttpSolrServer only for searching?
So in my architecture with the EmbeddedSolrServer I want to use the
advantage of direct API calls for indexing purpose and for searching I
would rely on HTTP requests.
I
yes. This works fine.
But make sure only one SolrServer is writing to the index at a time.
Also note that if you use the EmbeddedSolrServer to index and another
one to read, you will need to call commit/ on the 'read only' server
to refresh the index view (the work commit is a bit
...@gmail.com]
Sent: Monday, February 09, 2009 8:34 PM
To: solr-user@lucene.apache.org
Subject: Re: Combination of EmbeddedSolrServer and CommonHttpSolrServer
yes. This works fine.
But make sure only one SolrServer is writing to the index at a time.
Also note that if you use the EmbeddedSolrServer
Keep in mind that the way lucene/solr work is that the results are
constant from when you open the searcher. If new documents are added
(without re-opening the searcher) they will not be seen.
commit/ tells solr to re-open the index and see the changes.
1. Does this mean that
