[ https://issues.apache.org/jira/browse/SOLR-10272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15922798#comment-15922798 ]
Varun Thacker commented on SOLR-10272: -------------------------------------- Hi Erick, Okay I should have been more descriptive here. Today the start script works like this when we create a collection {code} ~/solr-6.4.2$ ./bin/solr create -c test Connecting to ZooKeeper at localhost:9983 ... INFO - 2017-03-13 12:28:04.069; org.apache.solr.client.solrj.impl.ZkClientClusterStateProvider; Cluster at localhost:9983 ready Uploading /Users/varunthacker/solr-6.4.2/server/solr/configsets/data_driven_schema_configs/conf for config test to ZooKeeper at localhost:9983 Creating new collection 'test' using command: http://localhost:7574/solr/admin/collections?action=CREATE&name=test&numShards=1&replicationFactor=1&maxShardsPerNode=1&collection.configName=test { "responseHeader":{ "status":0, "QTime":2555}, "success":{"192.168.0.4:7574_solr":{ "responseHeader":{ "status":0, "QTime":1425}, "core":"test_shard1_replica1"}}} {code} Given that this Jira adds a default configset and uses that if no "collection.configName" is present , we can remove this logic from the create command as this will be done automatically {code} Connecting to ZooKeeper at localhost:9983 ... INFO - 2017-03-13 12:28:04.069; org.apache.solr.client.solrj.impl.ZkClientClusterStateProvider; Cluster at localhost:9983 ready Uploading /Users/varunthacker/solr-6.4.2/server/solr/configsets/data_driven_schema_configs/conf for config test to ZooKeeper at localhost:9983 {code} > Use a default configset and make the configName parameter optional. > ------------------------------------------------------------------- > > Key: SOLR-10272 > URL: https://issues.apache.org/jira/browse/SOLR-10272 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public) > Reporter: Varun Thacker > > This Jira's motivation is to improve the creating a collection experience > better for users. > To create a collection we need to specify a configName that needs to be > present in ZK. When a new user is starting Solr why should he worry about > having to know about configsets before he can can create a collection. > When you create a collection using "bin/solr create" the script uploads a > configset and references it. This is great. We should extend this idea to API > users as well. > So here is the rough outline of what I think we can do here: > 1. When you start solr , the bin script checks to see if > "/configs/_baseConfigSet" znode is present . If not it uploads the > "basic_configs". > We can discuss if its the "basic_configs" or something other default config > set. > Also we can discuss the name for "/_baseConfigSet". Moving on though > 2. When a user creates a collection from the API > {{admin/collections?action=CREATE&name=gettingstarted}} here is what we do : > Use https://cwiki.apache.org/confluence/display/solr/ConfigSets+API to copy > over the default config set to a configset with the name of the collection > specified. > collection.configName can truly be an optional parameter. If its specified we > don't need to do this step. > 3. Have the bin scripts use this and remove the logic built in there to do > the same thing. -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org