lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Derek Poh <d...@globalsources.com>
Subject Re: Define search query parameters in Solr or let clients applications craft them?
Date Wed, 15 Jun 2016 00:20:35 GMT
Hi Emir

Yaguess one way is to implement a policy where new queries from client 
application have to be reviewcouple with periodic search log grooming as 
you have suggested.

On 6/14/2016 4:12 PM, Emir Arnautovic wrote:
> Hi Derek,
> Unless you lock all your parameters, there will always be a chance of 
> inefficient queries. Only way to fight that is to have full control of 
> Solr interface and provide some search API, or to do regular search 
> log grooming.
>
> Emir
>
> On 14.06.2016 03:05, Derek Poh wrote:
>> Hi Emir
>>
>> Thank you for pointing out the cons of defining them in Solr config.
>>
>> One of the thing I am worry about in letting clientapplication 
>> defined the parametersis the developers will use or include 
>> unnecessary, wrong and resource intensive parameters.
>>
>>
>> On 6/13/2016 5:50 PM, Emir Arnautovic wrote:
>>> Hi Derek,
>>> Maybe I am looking this from perspective who is working with other 
>>> peoples' setups, but I prefer when it is defined in Solr configs: I 
>>> can get sense of queries from looking at configs, you have mechanism 
>>> to lock some parameters, updates are centralized... However, it does 
>>> come with some cons: it is less expressive than what you can do in 
>>> client code, you have to reload cores when you want to change, 
>>> people tend to override it from client so you get configs in two 
>>> places.
>>>
>>> HTH,
>>> Emir
>>>
>>> On 13.06.2016 05:21, Derek Poh wrote:
>>>> Hi
>>>>
>>>> Would like to get some advice on should the queries parameters be 
>>>> define in Solr or let the clients applications define and pass the 
>>>> queries parameters to Solr?
>>>>
>>>> Regards,
>>>> Derek
>>>>
>>>>
>>>>
>>>> ----------------------
>>>> CONFIDENTIALITY NOTICE
>>>> This e-mail (including any attachments) may contain confidential 
>>>> and/or privileged information. If you are not the intended 
>>>> recipient or have received this e-mail in error, please inform the 
>>>> sender immediately and delete this e-mail (including any 
>>>> attachments) from your computer, and you must not use, disclose to 
>>>> anyone else or copy this e-mail (including any attachments), 
>>>> whether in whole or in part.
>>>> This e-mail and any reply to it may be monitored for security, 
>>>> legal, regulatory compliance and/or other appropriate reasons.
>>>
>>
>>
>> ----------------------
>> CONFIDENTIALITY NOTICE
>> This e-mail (including any attachments) may contain confidential 
>> and/or privileged information. If you are not the intended recipient 
>> or have received this e-mail in error, please inform the sender 
>> immediately and delete this e-mail (including any attachments) from 
>> your computer, and you must not use, disclose to anyone else or copy 
>> this e-mail (including any attachments), whether in whole or in part.
>> This e-mail and any reply to it may be monitored for security, legal, 
>> regulatory compliance and/or other appropriate reasons.
>


----------------------
CONFIDENTIALITY NOTICE 

This e-mail (including any attachments) may contain confidential and/or privileged information.
If you are not the intended recipient or have received this e-mail in error, please inform
the sender immediately and delete this e-mail (including any attachments) from your computer,
and you must not use, disclose to anyone else or copy this e-mail (including any attachments),
whether in whole or in part. 

This e-mail and any reply to it may be monitored for security, legal, regulatory compliance
and/or other appropriate reasons.
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message