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
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
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
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
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,
