[ 
https://issues.apache.org/jira/browse/SOLR-17862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18013779#comment-18013779
 ] 

Chris M. Hostetter commented on SOLR-17862:
-------------------------------------------

It's easy to see that changes to one collection impact other collections.

Setup two collections using the same configset:
{noformat}
$ ./solr/packaging/build/dev/bin/solr start -e cloud --no-prompt
...
$ curl 
'http://localhost:8983/solr/admin/collections?action=CREATE&name=xxxx&collection.configName=gettingstarted&numShards=1'\
...
$ curl 'http://localhost:8983/api/collections/xxxx/config/overlay'
{
  "responseHeader":{
    "status":0,
    "QTime":3
  },
  "overlay":{
    "znodeVersion":-1
  }
}
$ curl 'http://localhost:8983/api/collections/gettingstarted/config/overlay'
{
  "responseHeader":{
    "status":0,
    "QTime":3
  },
  "overlay":{
    "znodeVersion":-1
  }
}
{noformat}

Then attempt to modify one collection:

{noformat}
$ curl -X POST -H 'Content-type: application/json' -d 
'{"set-property":{"updateHandler.autoCommit.maxTime":12345}}' 
http://localhost:8983/api/collections/xxxx/config
...
$ curl 'http://localhost:8983/api/collections/xxxx/config/overlay'
{
  "responseHeader":{
    "status":0,
    "QTime":1
  },
  "overlay":{
    "znodeVersion":0,
    "props":{
      "updateHandler":{
        "autoCommit":{
          "maxTime":12345
        }
      }
    }
  }
}
$ curl 'http://localhost:8983/api/collections/gettingstarted/config/overlay'
{
  "responseHeader":{
    "status":0,
    "QTime":0
  },
  "overlay":{
    "znodeVersion":0,
    "props":{
      "updateHandler":{
        "autoCommit":{
          "maxTime":12345
        }
      }
    }
  }
}
{noformat}

> Config API is not per-collection; applies to all collections using the same 
> configset
> -------------------------------------------------------------------------------------
>
>                 Key: SOLR-17862
>                 URL: https://issues.apache.org/jira/browse/SOLR-17862
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Chris M. Hostetter
>            Priority: Major
>
> The "Config API" uses a URL path prefix of 
> {{/api/collections/<<COLLECTION_NAME>>/config}} and [has documentation that 
> says|https://solr.apache.org/guide/solr/latest/configuration-guide/config-api.html]...
> {quote}
> All Config API endpoints are collection-specific, meaning this API can 
> inspect or modify the configuration for a single collection at a time.
> {quote}
> ...but this is a lie.  Using the Config API to modify any aspect of a 
> collection actually modifies the {{configoverlay.json}} in the configset, and 
> impacts all collections using that configset.
> ----
> * The "Config API" should be changed to use some new a URL path prefix that 
> is specific to the name of the configset (Example: 
> {{/api/configset-props/<<CONFIGSET_NAME>>/}}) 
> * The Existing {{/api/collections/<<COLLECTION_NAME>>/config}} URL should be 
> deprecated
> * Documentation should be updated accordingly



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to