Yep, you're on the right track here. Look at classes that implement QueryResponseWriter, perhaps CSVResponseWriter our XMLResponseWriter might be good places to start.
They get a SolrQueryResponse that contains the returned list... Best Erick On Mon, Nov 7, 2011 at 2:29 PM, Draconissa <ariel.r...@ldschurch.org> wrote: > > Chris Hostetter-3 wrote: >> >> Agreed. In 3.x and below this type of logic is expected to live in the >> QueryResponseWriters. >> > > Forgive my ignorance, but where do QueryResponseWriters live? And where do > they fit into the flow? > > I know how the different components fit into a distributed search, and how > all the stages flow, but I haven't seen anything about response writers... > > Would it be something like using the distributed search and components to > retrieve the doc_ids and facets, and once the entire distributed search is > complete, a ResponseWriter would take the results (which is just doc ids > since we didn't use the get_fields or any Database component), queries our > SQL database, and creates the final response that gets sent to the client? > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/How-to-use-an-External-Database-for-Fields-tp3468308p3487972.html > Sent from the Solr - User mailing list archive at Nabble.com. >
