Description
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
updateHandler.autoCommit.maxDocs query.filterCache.initialSize
The api will be modeled around the bulk schema API
curl http://localhost:8983/solr/collection1/config -H 'Content-type:application/json' -d '{ "set-property" : {"updateHandler.autoCommit.maxDocs":5}, "unset-property": "updateHandler.autoCommit.maxDocs" }'
//or use this to set ${mypropname} values curl http://localhost:8983/solr/collection1/config -H 'Content-type:application/json' -d '{ "set-user-property" : {"mypropname":"my_prop_val"}, "unset-user-property":{"mypropname"} }'
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
Attachments
Attachments
Issue Links
- causes
-
SOLR-16178 ZkController#fireEventListeners thread should be shutdown on close
- Resolved
- depends upon
-
SOLR-6654 add a standard way to listen to config changes in cloud mode
- Resolved