You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Saïd Radhouani <r....@gmail.com> on 2010/06/21 22:29:08 UTC
Re: Configuring RequestHandler in solrconfig.xml OR in the Servlet code using SolrJ
I completely agreed. Thanks a lot!
-S
On Jun 21, 2010, at 9:08 PM, Abdelhamid ABID wrote:
> Why would someone port the solr config into servlet code ?
> IMO the first option would be the best choice, one obvious reason is that,
> when alter the solr config you only need to restart the server, whereas
> changing in the source drive you to redeploy your app and restart the
> server.
>
>
>
> On 6/21/10, Saïd Radhouani <r....@gmail.com> wrote:
>>
>> Hello,
>>
>> I'm developing a Web application that communicate with Solr using SolrJ. I
>> have three search interfaces, and I'm facing two options:
>>
>> 1- Configuring one SearchHandler per search interface in solrconfig.xml
>>
>> Or
>>
>> 2- Write the configuration in the java servlet code that is using SolrJ
>>
>> It there any significant difference between these two options ? If yes,
>> what's the best choice?
>>
>> Thanks,
>>
>> -Saïd
>
>
>
>
> --
> Abdelhamid ABID
> Software Engineer- J2EE / WEB
Re: Configuring RequestHandler in solrconfig.xml OR in the Servlet
code using SolrJ
Posted by Sven Maurmann <sv...@kippdata.de>.
Hi,
there are reasons for both options. Usually it is a good idea to put the
default
configuration into the solrconfig.xml (and even fix some of the
configuration) in
order to have simple client-side code.
But sometimesit is necessary to have some flexibility for the actual query.
In this
situation one would use the client-side approach. If done right, this does
not mean
to put the parameters in the servlet code.
Cheers,
Sven
--On Dienstag, 22. Juni 2010 17:52 +0200 "Jan Høydahl / Cominvent"
<ja...@cominvent.com> wrote:
> Hi,
>
> Sometimes I do both. I put the defaults in solrconfig.xml and thus have
> one place to define all kind of low-level default settings.
>
> But then I make a possibility in the application space to add/override
> any parameters as well. This gives you great flexibility to let server
> administrators (with access to solrconfig.xml) tune low level stuff, but
> also gives programmers a middle layer to put domain-space config instead
> of locking it down on the search node or up in the web interfaces.
>
> --
> Jan Høydahl, search solution architect
> Cominvent AS - www.cominvent.com
> Training in Europe - www.solrtraining.com
>
> On 21. juni 2010, at 22.29, Saïd Radhouani wrote:
>
>> I completely agreed. Thanks a lot!
>>
>> -S
>>
>> On Jun 21, 2010, at 9:08 PM, Abdelhamid ABID wrote:
>>
>>> Why would someone port the solr config into servlet code ?
>>> IMO the first option would be the best choice, one obvious reason is
>>> that, when alter the solr config you only need to restart the server,
>>> whereas changing in the source drive you to redeploy your app and
>>> restart the server.
>>>
>>>
>>>
>>> On 6/21/10, Saïd Radhouani <r....@gmail.com> wrote:
>>>>
>>>> Hello,
>>>>
>>>> I'm developing a Web application that communicate with Solr using
>>>> SolrJ. I have three search interfaces, and I'm facing two options:
>>>>
>>>> 1- Configuring one SearchHandler per search interface in solrconfig.xml
>>>>
>>>> Or
>>>>
>>>> 2- Write the configuration in the java servlet code that is using SolrJ
>>>>
>>>> It there any significant difference between these two options ? If yes,
>>>> what's the best choice?
>>>>
>>>> Thanks,
>>>>
>>>> -Saïd
>>>
>>>
>>>
>>>
>>> --
>>> Abdelhamid ABID
>>> Software Engineer- J2EE / WEB
Re: Configuring RequestHandler in solrconfig.xml OR in the Servlet code using SolrJ
Posted by Jan Høydahl / Cominvent <ja...@cominvent.com>.
Hi,
Sometimes I do both. I put the defaults in solrconfig.xml and thus have one place to define all kind of low-level default settings.
But then I make a possibility in the application space to add/override any parameters as well. This gives you great flexibility to let server administrators (with access to solrconfig.xml) tune low level stuff, but also gives programmers a middle layer to put domain-space config instead of locking it down on the search node or up in the web interfaces.
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
Training in Europe - www.solrtraining.com
On 21. juni 2010, at 22.29, Saïd Radhouani wrote:
> I completely agreed. Thanks a lot!
>
> -S
>
> On Jun 21, 2010, at 9:08 PM, Abdelhamid ABID wrote:
>
>> Why would someone port the solr config into servlet code ?
>> IMO the first option would be the best choice, one obvious reason is that,
>> when alter the solr config you only need to restart the server, whereas
>> changing in the source drive you to redeploy your app and restart the
>> server.
>>
>>
>>
>> On 6/21/10, Saïd Radhouani <r....@gmail.com> wrote:
>>>
>>> Hello,
>>>
>>> I'm developing a Web application that communicate with Solr using SolrJ. I
>>> have three search interfaces, and I'm facing two options:
>>>
>>> 1- Configuring one SearchHandler per search interface in solrconfig.xml
>>>
>>> Or
>>>
>>> 2- Write the configuration in the java servlet code that is using SolrJ
>>>
>>> It there any significant difference between these two options ? If yes,
>>> what's the best choice?
>>>
>>> Thanks,
>>>
>>> -Saïd
>>
>>
>>
>>
>> --
>> Abdelhamid ABID
>> Software Engineer- J2EE / WEB
>