Here is what I got so far.
I can add shard.qt parameter to the query string along with shards and qt,
then distributed version of my component is working.
Otherwise "process" function in my custom component is not called, only
default SolrCore "execute".
It seems like a hacky approach to the pr
Seems like my problem could be that qt parameter is not passed.
I see it in the createMainQuery and then after it in SolrCore execute params
do not have qt in there.
It appears that in SearchHandle:
String shardHandler = req.getParams().get(ShardParams.SHARDS_QT);
if (shardHandler == null) {
On Thu, Sep 18, 2008 at 7:57 PM, outre <[EMAIL PROTECTED]> wrote:
>
> So is any code from solr-303 going to merged with latest solr trunk?
I'm not sure about your problem but SOLR-303 is already committed and has
been released with Solr 1.3
> I saw a post about localsolr being donated to solr.
May be if I expand on it a bit ?
Basically, I want localsolr to work with the latest trunk of the solr. And
it seems to work just fine, but the distributed version doesn't work. Even
though looking at the comments it seems the modes from solr-303 were planned
to be moved to the latest code base
