I don't think I'm quite getting this. Instead of going down that low, could you make your own ResponseWriter? That has access to all the information in the doc, and it seems like you could reach out to the DB at that point and get your information merrily adding it to the docs.
Or you could have your application layer look at the returned data and do the same thing. If I'm completely off base, I guess I don't get what values you're "values you are exposing and messing with", can you give some examples? Best Erick On Mon, Oct 31, 2011 at 12:50 PM, Draconissa <ariel.r...@ldschurch.org> wrote: > Hello all. > > I have a question about using an external database to store just the fields > returned during the GET_FIELDS stage. > > We are using Solr to search an index with a good number of columns. That > returns some ids, the scores and some facets. The ids are then passed to a > custom DatabaseComponent that queries a SQL Database for the ids and returns > the data that we actually want to display. > > However, to make this work (and it does) we have had to make some values > public in the ResponseBuilder and elsewhere, so that we can pull the ids out > and use them in the GET_FIELDS stage to actually fetch the SQL data. The > values we are exposing and messing with in our code shouldn't be messed > with, really, being cited as "shared" or "should be treated as shared." > > After a fair amount of investigation, however, we have been unable to find > another way to pull the results from the GET_IDS *without* reaching into the > ResponseBuilder like we have. This seems like a serious oversight to me, > and I am afraid that we just don't know enough about how to accomplish the > same results without modifying Solr. > > So the main question is, Is there a way to use an external database > component without exposing some package protected variables inside Solr? > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/How-to-use-an-External-Database-for-Fields-tp3468308p3468308.html > Sent from the Solr - User mailing list archive at Nabble.com. >
