[jira] [Updated] (SOLR-6719) Collection API: CREATE ignores 'property.name' when creating individual cores

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[jira] [Updated] (SOLR-6719) Collection API: CREATE ignores 'property.name' when creating individual cores

JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/SOLR-6719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cassandra Targett updated SOLR-6719:
    Component/s: SolrCloud

> Collection API: CREATE ignores 'property.name' when creating individual cores
> -----------------------------------------------------------------------------
>                 Key: SOLR-6719
>                 URL: https://issues.apache.org/jira/browse/SOLR-6719
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>            Reporter: Hoss Man
> Yashveer Rana pointed this out in the ref guide comments...
> https://cwiki.apache.org/confluence/display/solr/Collections+API?focusedCommentId=47382851#comment-47382851
> * Collection CREATE is documented to support "property._name_=_value_" (where 'name' and 'property' are italics placeholders for user supplied key=val) as "Set core property _name_ to _value_. See core.properties file contents."
> * The [docs for core.properties|https://cwiki.apache.org/confluence/display/solr/Format+of+solr.xml#Formatofsolr.xml-core.properties_files] include a list of supported property values, including "name" (literal) as "The name of the SolrCore. You'll use this name to reference the SolrCore when running commands with the CoreAdminHandler."
> From these docs, it's reasonable to assume that using a URL like this...
> http://localhost:8983/solr/admin/collections?action=CREATE&name=my_collection&numShards=2&configSet=data_driven_schema_configs&property.name=my_corename
> ...should cause "my_collection" to be created, with the core name used for every replica being "my_corename" ... but that doesn't happen.  instead the replicas get core names like "my_collection_shard1_replica1"
> ----
> This is either a bug, or (my suspicion) it's intentional that the user specific core name is not being used -- if it's intentional, then the Collection CREATE command should fail with a clear error if a user does try to use "property.name" rather then silently ignoring it and the Collection CREATE docs should be updated to make it clear that "name" is an exception to the general property.foo -> foo in core.properties support.

This message was sent by Atlassian JIRA

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