You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Noble Paul (JIRA)" <ji...@apache.org> on 2015/01/07 07:29:35 UTC
[jira] [Comment Edited] (SOLR-6533) Support editing common
solrconfig.xml values
[ https://issues.apache.org/jira/browse/SOLR-6533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14267320#comment-14267320 ]
Noble Paul edited comment on SOLR-6533 at 1/7/15 6:28 AM:
----------------------------------------------------------
You are right, The {{/config}} is not aware of implicitly defined plugins. We need it to make it available
bq.Also, what's an example of /config/<component-name>
component names are requestHandler, searchComponent etc. I should document that
was (Author: noble.paul):
You are right, The {{/config}} is not aware of implicitly defined plugins. We need it to be made available
bq.Also, what's an example of /config/<component-name>
component names are requestHandler, searchComponent etc. I should document that
> Support editing common solrconfig.xml values
> --------------------------------------------
>
> Key: SOLR-6533
> URL: https://issues.apache.org/jira/browse/SOLR-6533
> Project: Solr
> Issue Type: Sub-task
> Reporter: Noble Paul
> Assignee: Noble Paul
> Fix For: 5.0, Trunk
>
> Attachments: SOLR-6533.patch, SOLR-6533.patch, SOLR-6533.patch, SOLR-6533.patch, SOLR-6533.patch, SOLR-6533.patch, SOLR-6533.patch, SOLR-6533.patch, SOLR-6533.patch, SOLR-6533.patch, SOLR-6533.patch
>
>
> 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
> {code}
> updateHandler.autoCommit.maxDocs
> query.filterCache.initialSize
> {code}
> The api will be modeled around the bulk schema API
> {code:javascript}
> curl http://localhost:8983/solr/collection1/config -H 'Content-type:application/json' -d '{
> "set-property" : {"updateHandler.autoCommit.maxDocs":5},
> "unset-property": "updateHandler.autoCommit.maxDocs"
> }'
> {code}
> {code:javascript}
> //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"}
> }'
> {code}
> 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}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org