Hello all, here I am with another question... :-)
I figured that I have to change approach to implement the requirements I have :-( Here it is what I have to index: 1) data "A" in an Oracle DB Table "A" 2) data "B" in an Oracle DB Table "B" 3) data "C" in different files 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". At first I thought of using only one Solr with different datasources, and one huge index, but I figured that delta imports would be very hard/expensive/impossible. Reading some other posts I thought that maybe a better approach would be as following: 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. 1) is a multicore architecture: I know it is possible and I tested that it works great 2) same as above, no problems here :-) 3) I want to "hide" the different cores to the client application; the 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? 5) I know this is just my business logic :-) Any thougts/warning/advice about this? Thanks a lot in advance! Giovanni