Hi, I have a few queries regarding this:
1. Does this mean that committing on the indexing (Embedded) server does not reflect the document changes when we fire a search through another (HTTP) server? 2. What happens to the commit fired on the indexing server? Can I remove that and just commit on the "read only" server? 3. Do we have to fire a Commit (on the HTTP server) before we try to search for a document? 4. Can we make any setting (perhaps using auto-commit) on the HTTP server to avoid this scenario? Thanks, Kumar -----Original Message----- From: Ryan McKinley [mailto:ryan...@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 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 misleading) ryan On Feb 9, 2009, at 9:43 AM, Bapat, Mayur wrote: > 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 tried some basic stuff but found that since the Solr core is being > initialized twice, I am unable to find the documents indexed through > the > embedded server using the HTTP requests unless I restart the tomcat. > Any > idea how it could be achieved? > > Mayur Bapat > PTC-Pune India > Ext - 3523
