Ah .... i was missunderstanding your goal of "doctypes" ... the use case i was thinking is that you have "book" documents and "movie" documents and you frequently only query on one type of the other but sometime you do a generic query on all of them using the fields they have in common.
this is clearly not the situation you are describing, since you suggest storing them in completley seperate indexes that can be blown away independently. there is a patch in Jira to support multiple SolrCore's in a single JVM "context" ... as i understand it this would achieve your goal (but i havne't really had a chance to look at it so i can't really speak to it. in general, running multiple Solr isnt'ances is actaully wuite easy and not as bad as you make it out to be ... the overhead of running multiple Solr webapp instances in a single JVM doesn't really take up that much more memory or CPU ... yes the classes are all loaded twice, but that typically pales in comparison to the amount of data involved in your index (unelss you've got hundrads of tiny indexes or something like that) : - more difficult to maintain the index. If I want to delete : all docs of a doc type, I can use deletet by query but it's : always easier to wipe out the whole index directory if doctypes : are kept separate but maintained by the same solr instance. : I can run two separate solr instances to achieve this then this : takes more memory/CPU/maintaince effort. : : One schema file with doctypes defined, and separate index directories : would be perfect, in my opinion :) or even separate schema files :) -Hoss
