: used to call the lucene IndexSearcher . As the documents are collected in
: TopDocs in Lucene , before that is passed back to Nutch , i used to look
: into the top K matching documents , consult some external repository
: and further score the Top K documents and reorder them in the TopDocs array
: . These reordered TopDocs is passed to Nutch . All these reordering code
: was implemented by Extending the lucene IndexSearcher class .
1) that's basically the same info you provided before -- it still doesn't
really tell us anything about what your current logic does with the top K
documents and how/why/when you decide to reorder them or by how much --
details that are kind of important in being able to provide you with any
meaningful advice on how to achieve your goal using hte plugin hooks
available in Solr.
2) if you only care about re-ordering the Top K documents using some
secret sauce, then i would suggest you just set rows=K and let Solr do
it's thing, the post process the reuslts -- either in your client, or in a
SearchComponent that modifies the SolrDocumentList produces by
QueryComponent.
: > can you elaborate on what exactly your "some logic" involves?
...
: > https://people.apache.org/~hossman/#xyproblem
: > XY Problem
: >
: > Your question appears to be an "XY Problem" ... that is: you are dealing
: > with "X", you are assuming "Y" will help you, and you are asking about "Y"
: > without giving more details about the "X" so that we can understand the
: > full issue. Perhaps the best solution doesn't involve "Y" at all?
: > See Also: http://www.perlmonks.org/index.pl?node_id=542341
-Hoss
