I had not heard of that technique before. Interesting! But couldn't you do the same thing with a unified schema spread among your cores?
Michael Della Bitta Applications Developer o: +1 646 532 3062 | c: +1 917 477 7906 appinions inc. “The Science of Influence Marketing” 18 East 41st Street New York, NY 10017 t: @appinions <https://twitter.com/Appinions> | g+: plus.google.com/appinions w: appinions.com <http://www.appinions.com/> On Wed, Jun 12, 2013 at 5:05 PM, smanad <sma...@gmail.com> wrote: > Is this a limitation of solr/lucene, should I be considering using other > option like using Elasticsearch (which is also based on lucene)? > But I am sure search in multiple indexes is kind of a common problem. > > Also, i as reading this post > > http://stackoverflow.com/questions/2139030/search-multiple-solr-cores-and-return-one-result-set > in one of the comments it says, > "So if I have Core0 with fields documentId,fieldA,fieldB and Core1 with > fields documentId,fieldC,fieldD. Then I create another core, lets say Core3 > with fields documentId,fieldA,fieldB,fieldC,fieldD. I will never be > importing data into this core? And then create a query handler, that > includes the shard parameter. So when I query Core3, it will never really > contain indexed data, but because of the shard searching it will fetch the > results from the other to cores, and "present" it on the 3rd core? Thanks > for the help! " > > Is that what I should be doing? So all the indexing still happens in > separate cores but searching happens in a one single core? > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Need-help-with-search-in-multiple-indexes-tp4070040p4070055.html > Sent from the Solr - User mailing list archive at Nabble.com. >
