I have the same situation now. If I don't want to use http connection, so I need to use EmbeddedSolrServer that what I think I need correct? We have Master/slaves solr, the applications use slaves for search. The Master only taking the new index from Database and slaves will pull the new index using snappuller/snapinstaller.
I don't want or try not to use http connection from Database to Solr Master because of network latency( very slow). Any suggestions? Francis -----Original Message----- From: Smiley, David W. [mailto:dsmi...@mitre.org] Sent: Wednesday, August 26, 2009 10:23 AM To: solr; Paul Tomblin Subject: Re: SolrJ and Solr web simultaneously? Once a commit occurs, all data added before it (by any & all clients) becomes visible to all searches henceforth. The "web interface" has direct access to Solr, and SolrJ remotely accesses that Solr. SolrEmbeddedSolrServer is something that few people should actually use. It's mostly for embedding Solr without running Solr as a server, which is a somewhat rare need. ~ David Smiley Author: http://www.packtpub.com/solr-1-4-enterprise-search-server On 8/26/09 1:14 PM, "Paul Tomblin" <ptomb...@xcski.com> wrote: Is Solr like a RDBMS in that I can have multiple programs querying and updating the index at once, and everybody else will see the updates after a commit, or do I have to something explicit to see others updates? Does it matter whether they're using the web interface, SolrJ with a CommonsHttpSolrServer or SolrJ with a EmbeddedSolrServer? -- http://www.linkedin.com/in/paultomblin
