Hi ,

        Thanks Chris. I had been using Nutch 1.1 . The Nutch IndexSearcher
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 .
                The lucene core that comes with solr is a bit different
from the one that used to come with Nutch 1.1 . As a result implementing
the same is not straight forward .Moreover , i cannot figure out at which
point exactly the SolrIndexSearcher makes a direct Interaction with
LuceneIndexSearcher .
               With FunctionQuery i loose the flexibility of looking into
the documents before passing to the final result set.

  Now i am using solr 3.4 and i would like to implement the same between
solr and lucene.

Thanks ,
Pom

On Wed, Apr 24, 2013 at 3:05 AM, Chris Hostetter
<hossman_luc...@fucit.org>wrote:

>
> : > > . For any query it passes through the search handler and solr finally
> : > > directs it to lucene Index Searcher. As results are matched and
> collected
> : > > as TopDocs in lucene i want to inspect the top K Docs , reorder them
> by
> : > > some logic and pass the final TopDocs to solr which solr may send as
> a
> : > > response .
>
> can you elaborate on what exactly your "some logic" involves?
>
> instead of writing a custom collector, using a function query may be the
> best solution.
>
> 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
>

Reply via email to