Hello there. I moved from Lucene to Solr and am thus far impressed with the speed, even with the added XML transport necessary to send and receive data.
However, one thing I did like about the Lucene implementation was the ability to specify indices for each invocation. I agree with Michael Bryzek's comments about extending Solr to include multiple indices. This would be an extremely useful feature for me, as I tend to place data into stratifications to maximize low seek times and data sizes. I'm currently looking to run multiple instances of Solr if necessary to handle this. Another possible way to implement multiple indices (in addition to Michael's suggestion through objectTypes) could be simply appending the index name to the query, similar to the following: via Indexing: <add index="products"> . </add> via Query: http://localhost/solr/select?index=products&q= . And either schema.xml broken into <index name="products">, or schema-<indexname>.xml could handle that particular schema. Regardless how it gets done, it would be extremely valuable to offer this functionality and afford a better deployment "strategy" for those of us dealing with different types of data. Thanks Yonik, Chris, and others for releasing this - it seems to work great for my needs. Brian --- Michael Bryzek wrote: a) Minimize the number of instances of SOLR. If I have 3 web applications, each with 12 database tables to index, I don't want to run 36 JVMs. I think introducing an objectType would address this.
