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 problem though, I am wondering if
there is better solution.
Thanks
outre wrote:
>
> 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) {
> params.remove(CommonParams.QT);
> } else {
> params.set(CommonParams.QT, shardHandler);
> }
>
> Where ShardParams.SHARDS_QT = "shards.qt".
>
> Should I change qt shards.qt then? Or is there another way?
>
>
> Thanks
>
>
> outre wrote:
>>
>> Hi,
>>
>> I am fairly new to solr, but I realize that the question I am about to
>> ask is fairly large.
>>
>> Is there any way to create a custom component that would compile and run
>> with the latest solr src and would be capable of doing distributed
>> search?
>>
>> I have looked at localsolr example and QueryComponent, created a similar
>> setup except for I was trying to compile with the latest code from svn.
>> It compiles fine but at run time I get access violation for
>> org/apache/solr/handler/component/ShardFieldSortedHitQueue.
>>
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/Distributed-custom-component-tp19517853p19562451.html
Sent from the Solr - Dev mailing list archive at Nabble.com.
