Hello and thanks for reading my question.
If our high-level search handler doesn't get enough results back from a Solr
query, it tweaks the query, re-sends to Solr, and combines the result sets
from the two queries. I would like to modify our Solr set-up so that Solr
itself could handle the deciding, tweaking, re-sending and combining within
a single call.
My current thought is to create a FollowUpQueryComponent that would live in
the "last-components" section of the definition of our usual requestHandler
in solrconfig.xml.
The new component would take a look at the results of the default
QueryComponent and decide whether or not to tweak the query and bring about
another search. I tried to do the looking-and-tweaking at the aggregator
level in the new component's prepare() function, but ran into two problems.
1) The new component's prepare() function is called before the default
QueryComponent has done its work, so it doesn't have the information it
needs to decide whether the new call will be needed or not, and
2) Even if I postpone the decision until after the default QueryComponent's
results are in, as far as I can tell those results stay on the shards and
are not available to the aggregator.
Either I am going about this all wrong, or these must be standard problems
for creators of custom QueryComponents. Are there standard solutions? Any
feedback would be much appreciated.
Thanks,
Jitka
--
View this message in context:
http://lucene.472066.n3.nabble.com/search-component-needs-access-to-results-of-previous-component-tp4138335.html
Sent from the Solr - User mailing list archive at Nabble.com.
