Hi,
We are looking at running read-only solr nodes embedded in our webapp
nodes. This would give us the
additional features of solr over lucene, but would keep it in memory and
reduce the overhead of http/xml
transport of results.
Looks like we would just create a request handler and call
handleRequest(req,rsp), and deal with the
search results DocList ourselves.
Would there be any reason why this sort of setup would prohibit the use
of index replication in a master/slave
setup?
Does this make sense? As you might guess, speed is more important that
flexibility. We are using solr for
a content search, returning ids, and doing a secondary db lookup for
extended entity information.
Thanks --Joachim
