You're probably looking at two custom components. To get started, look in solrconfig.xml for first-component and last-component. BTW, writing custom components isn't all that hard once you get to the place to start...
Anyway, your first component reaches out to your other data source and "does the right thing" to the incoming query based on what it finds in the external source. You either write a last-component or use a DocTransformer (new in 4.x) to change the document on the way out. DocTransformer is probably best, although I haven't personally written one yet but they seem to be The New Way. There's nothing equivalent for the query bits that I know of though.... Best Erick On Fri, Apr 5, 2013 at 8:28 AM, Maciej Liżewski <maciej.lizew...@3e.pl> wrote: > Ok., my case is like this: I have Solr index with some documents that must > be left intact. I also need to store somewhere else some data related to > documents in Solr (it can be SQL database or another Solr core). > > In other words - I need to have some data stored independently to main Solr > index (for example tagging, user-rating, etc), but I need then to use such > data in queries to the Solr index. > > Now - what I need to extend/replace to be able to: > > 1) filter Solr queries with such remote data (I can fetch IDs of > documents that should be listed and I need to intersect it somehow with > query results)? > > 2) Somehow extend returned results (documents itself or as additional > section in response similar to highlighter) and provide related data (from > external source) with selected documents. > > > > Any help appreciated. > > > > -- > > Maciej Liżewski >
