: Data "A", "B", and "C" are slightly different, thus they are indexed
: differently; obviously the client receives the search results for all data
: types in a consistent/common format. The client application shall be able to
: search among each or all data types ("A", "B", "C"). The order will be
: configurable, like: return the first 5 from data "A", the first 10 from "B",
: all "C".generally speaking, when people say they have data from X different sources, but they want them all returned in a unified list of results, i advocate for having a single index -- but if you have a specific need to be able to pick and choose how many results you get from each "set" then using seperate cores (either on seperate machines, or in a multicore setup) as you outlined below does seem like a more logical choice.... : 1) one Solr core for each data type (one for "A", one for "B", one for "C") : 2) one index fora each data type, thus one document type for "A", one for : "B", and one for "C" : 3) client applications shall be able to search on one or all cores : 4) the cores shall return search results in a common XML format : 5) search results shall be aggregated in a configurable way : : Can you please tell me if this architecture is possible with Solr? Obviously : I am not looking for an "out-of-the-.box" solution, I just need to : understand what I have to develop myself and what is already available. it's certainly possible, but these aggregation pieces (with your custom biz rules) would need to be implemented yourself. : client application should send the requests to one "guy" that parses the : request and forwards it to the cores. Is this a custom RequestHandler? Any : link (to the Wiki?) to understand better? Or is there anything already : available to achieve this? : 4) The "guy" that parses the request and forwards it to the cores shall : aggregate and return results in a common XML format: is this a custom : ResponseHandler? it could be a custom request handler, but it doesn't have to be -- you could implment it in whatever way is easiest for you (there's no reason why it has to run in the same JVM or on the same physical machine as Solr ... it could be a PHP script on another server if you want) -Hoss
