Thanks Chris, yes, that makes sense. I'll do some more experimenting along
the lines of HitCollector in solr and from my standalone programs as well.
If I yield meaningful resolution and it would benefit the community (if
there's interest) I'll do a concept patch as you mentioned.
-koji
On
Hi Chris,
My last email msg was in response to your suggestion:
If it's a Lucene class, you may want to start by making a small proof
of concept RMI app that just uses the Lucene core classes, once that
works then try your changes in Solr.
For which I agree is a good starting point to narrow
: My last email msg was in response to your suggestion:
:
: If it's a Lucene class, you may want to start by making a small proof
: of concept RMI app that just uses the Lucene core classes, once that
: works then try your changes in Solr.
:
: For which I agree is a good starting point to
Hi,
I am looking at extending the source code for SolrIndexSearcher for my own
purposes. Basically, I am trying to replace the use of Lucene's
IndexSearcher with a ParallelMultiSearcher version so that I can have a
query search both locally available indexes as well as remote indexes
available
core classes, once that
works then try your changes in Solr.
: Date: Tue, 9 May 2006 02:32:45 -0700
: From: Koji Miyamoto [EMAIL PROTECTED]
: Reply-To: solr-user@lucene.apache.org
: To: solr-user@lucene.apache.org
: Subject: extending SolrIndexSearcher
:
: Hi,
:
: I am looking at extending
: IndexSearcher. I replaced it with ParallelMultiSearcher, where it is
: initialized similar to the client code I mentioned above.
:
: From that, it seems like Solr itself needs to marshall and unmarshall the
: searcher instance SolrIndexSearcher holds, and because the
: ParallelMultiSearcher is
