lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander S. (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (SOLR-11939) Collection API: property.name ignored when creating collections
Date Fri, 02 Feb 2018 15:08:00 GMT

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

Alexander S. edited comment on SOLR-11939 at 2/2/18 3:07 PM:
-------------------------------------------------------------

Found this discussion [http://lucene.472066.n3.nabble.com/Core-property-name-ignored-when-creating-collection-using-API-td4183405.html]

It seems like I don't have to worry about the core name as it seems Solr is mowing towards
collections.

UPD. But this is still a discrepancy between the docs and the API. I've spent an hour figuring
this out, patching a Chef's cookbook adding these properties and figured out that this doesn't
work as described in the docs. 


was (Author: aheaven):
Found this discussion [http://lucene.472066.n3.nabble.com/Core-property-name-ignored-when-creating-collection-using-API-td4183405.html]

It seems like I don't have to worry about the core name as it seems Solr is mowing towards
collections.

> Collection API: property.name ignored when creating collections
> ---------------------------------------------------------------
>
>                 Key: SOLR-11939
>                 URL: https://issues.apache.org/jira/browse/SOLR-11939
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>    Affects Versions: 5.3.1
>            Reporter: Alexander S.
>            Priority: Major
>
> Trying to create a collection this way:
> {code:java}
> /solr/admin/collections?wt=json&action=CREATE&name=carmen-test&replicationFactor=1&numShards=4&shards=shard1,shard2,shard3,shard4&collection.configName=carmen&router.name=compositeId&property.name=carmen_test{code}
> This appears in the log:
> {code:java}
> OverseerCollectionProcessor.processMessage : create , {
>   "name":"carmen-test",
>   "fromApi":"true",
>   "replicationFactor":"1",
>   "collection.configName":"carmen",
>   "numShards":"4",
>   "shards":"shard1,shard2,shard3,shard4",
>   "stateFormat":"2",
>   "property.name":"carmen_test",
>   "router.name":"compositeId",
>   "operation":"create"}{code}
> But the resulting core name is *carmen-test_shard1_replica1* matching "collection name"
+ sharn name + replica number.
> How can I set a custom core name when creating a collection?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message