On 4/10/06, Chris Hostetter <[EMAIL PROTECTED]> wrote: > : In looking at the code, it looks like it'd be difficult to do this > : without actually doing an HTTP POST. Or is there a clean way to > : leverage Solr's infrastructure without POSTing into it? I don't even > : need Solr running while indexing. Is this possible easily? If so > : what API should I be using? > > To answer your implicit question: in the past the only > recommended/supported way to get documents into Solr was by POSTing > <add> document messages.
Yes, updating a running Solr server is the recommended (and more flexible) approach. > I know Yonik has wanted to make it easier it easier, having a client > library that uses the SolrCore directly seems like a good start. To me, running Solr outside the webapp is "expert" level use, and not something I'd want to generally recommend. For an official client library, I'd rather have something that managed HTTP communications & serialization to a running Solr server: - It's not an exclusive client, can coexist with other updaters/searchers - can be used for rebuilding whole index as well as incremental updates - could possibly be used as an alternate replication strategy... do the updates to multiple Solr instances. -Yonik
