Although the goal of this project is to maintain and discuss common configs across projects, there will be times when people want to customize the configs to fit a certain purpose. This might be something like configuring HA, changing the maxTime directive for development environments, etc. It might be useful for the module to be a "schema customizer", that based on the default config would allow for changing some values via the GUI and spitting out an xml file. There could be drush integration so that people could use it to generate varying configs on the fly to aide in deployment.

Comments

cpliakas’s picture

Also, the goal of the module is not to be a dependency of Apache Solr Search Integration / Search API. This project will house the "master" copy of the configs, but the config file generator will be a standalone tool to help with customizations.

nick_vh’s picture

And more importantly : multilanguage...!

If this module could generate the proper multilanguage schema.xml/solrconfig.xml + the proper protwords/stopwords that would be awesome! However, I think some website would be able to do this in a more intuitive way?

drunken monkey’s picture

First things first, I'd say, but a config file generator / customiser could certainly be useful. Having this online somewhere would be more useful, probably, but also more work to maintain, so I guess having this module do that is more than enough.

drunken monkey’s picture

But by the way, when are we going to tackle the 1.4 configs? Wouldn't this be better done in parallel to the 3.x configs, as the discussion will probably largely be about the same settings?

nick_vh’s picture

I guess we can finalize the settings for 3.5 and then see how we backport it. Most of it is backwards compatibly since we do not use some of the cutting edge new stuff such as tieredmergepolicy.

I'll take it on me to test the configs regularly in 1.4 and 3.5/3.6

cpliakas’s picture

Good points, Thomas, and thanks, Nick, for offering to pick up some of this work!

nick_vh’s picture

Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.