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 5/10
: 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 na
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
: 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
I tried it with just Lucene + RMI, and that works just fine. It's actually
based on the Lucene In Action e-book topic on how to use
ParallelMultiSearcher (chap.5). The relevant code snippet follows:
/*
* search server:
* This is the code frag for the search server, which enters
* a wait-loop to
I don't really know a lot about RMI, but as i understand it, Serialization
is a core neccessity -- if the arguments you want to pass to your Remote
Method aren't serializable, then RMI can't pass those argument across the
wire.
That said: it's not clear to me from the psuedocode/stacktrace you
in
