There are a bunch of properties in solrconfig.xml which users want to edit. We will attack them first
These properties will be persisted to a separate file called config.json (or whatever file). Instead of saving in the same format we will have well known properties which users can directly edit
The api will be modeled around the bulk schema API
The values stored in the config.json will always take precedence and will be applied after loading solrconfig.xml.
- An http GET on /config path will give the real config that is applied .
- An http GET of/config/overlay gives out the content of the configOverlay.json
- /config/<component-name> gives only the child of the same name from /config . example: /config/requestHandler , /config/searchComponent