On 4/13/07, Henrib <[EMAIL PROTECTED]> wrote:
I'm trying to choose between embedding Lucene versus embedding Solr in one webapp. In Solr terms, functional requirements would more or less lead to multiple schema & conf (need CRUD/generation on those) and deployment constraints imply one webapp instance.
Do you really need multiple schema's? multiple indexes? This has been posted many times (i thought i needed it too!) - it turns out most cases can easily be taken care of by putting multiple document types in the same index and including a "type" field. You could have a single schema with names for common fields, or one that has a prefix for each type; either "title" or "typeA_title", "typeB_title" - the common name approach can be easier because it makes it easier to search across types.
-Embed Solr but refactor 'some' of its core, assuming it is correct to see one Solr core as the association of one schema & one conf.
If you absolutely need multiple indexes, It will probably be easier to fudge the single webapp requirement then to refactor solr to remove the static singleton SolrCore.getSolrCore(). ryan
