Good question, Mikhail. I started by putting that logic in the prepare()
function by sheer force of habit, but have since moved it first to
distributedProcess() (my system is sharded) and now to handleResponses() (as
in MoreLikeThisComponent.java, which I am mimicking without understanding).
As o
Hello Jitka,
I wonder why you put the custom component logic into prepare() but not in
process()?
28.05.2014 1:55 пользователь "Jitka" написал:
> 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 qu
Thanks for your reply. I'll check out that link.
--
View this message in context:
http://lucene.472066.n3.nabble.com/search-component-needs-access-to-results-of-previous-component-tp4138335p4139409.html
Sent from the Solr - User mailing list archive at Nabble.com.
Better to implement this first at your application layer, and when you are
finally happy with the results then consider pushing it down into Solr, or
even better, leave it at the application level.
You might want to take a look at the "Unsupervised Feedback" feature of the
LucidWorks Search So
