lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shalin Shekhar Mangar <shalinman...@gmail.com>
Subject Re: Index and query time suggester behavior in a SolrCloud environment
Date Thu, 20 Apr 2017 09:11:28 GMT
Comments inline:


On Wed, Apr 19, 2017 at 2:46 PM, Andrea Gazzarini <gxsubs@gmail.com> wrote:
> Hi,
> any help out there?
>
> BTW I forgot the Solr version: 6.5.0
>
> Thanks,
> Andrea
>
>
> On 18/04/17 11:45, Andrea Gazzarini wrote:
>>
>> Hi,
>> I have a project, with SolrCloud, where I'm going to use the Suggester
>> component (BlendedInfixLookupFactory with DocumentDictionaryFactory).
>> Some info:
>>
>>   * I will have a suggest-only collection, with no NRT requirements
>>     (indexes will be updated with a daily frequency)
>>   * I'm not yet sure about the replication factor (I have to do some
>>     checks)
>>   * I'm using Solrj on the client side
>>
>> After reading some documentation I have a couple of doubts:
>>
>>   * how the *suggest.build* command is working? Can I issue this
>>     command towards just one node, and have that node forward the
>>     request to the other nodes (so each of them can build its own
>>     suggester index portion)?

The suggest.build only builds locally in the node to which you sent
the request. This makes it a bit tricky because if you send that
command with just the collection name, it will be resolved to a local
core and executed there. The safest/easiest way is to set
buildOnCommit or buildOnOptimize in the suggester configuration.

>>   * how things are working at query time? Can I use send a request
>>     with only suggest.q=... to my /suggest request handler and get
>>     back distributed suggestions?

The SuggestComponent works in distributed mode and it will request and
merge results from all shards.

>>
>> Thanks in advance
>> Andrea
>
>



-- 
Regards,
Shalin Shekhar Mangar.

Mime
View raw message