[ https://issues.apache.org/jira/browse/SOLR-6767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14230647#comment-14230647 ]
Timothy Potter commented on SOLR-6767: -------------------------------------- I committed a fix that affects this. Now, when you do: {code} bin/solr -e techproducts {code} The script does the following when creating the techproducts core: {code} mkdir -p server/solr/techproducts cp -r server/solr/configsets/sample_techproducts_configs/conf server/solr/techproducts/conf {code} This leaves the {{configsets/sample_techproducts_configs}} untouched. I believe adding some UI support for the configsets is a must-have for 5.0 release. Ideally, the user will be able to go to the Admin UI and create a new core by only providing a name and selecting a configset from a drop down. > Improve user experience when starting Solr in standalone mode using scripts > --------------------------------------------------------------------------- > > Key: SOLR-6767 > URL: https://issues.apache.org/jira/browse/SOLR-6767 > Project: Solr > Issue Type: Bug > Components: scripts and tools, web gui > Reporter: Anshum Gupta > > As of now, starting Solr in standalone mode using './solr start' starts up > Solr without any core. Trying to create a core from coreadmin UI doesn't work > and errors out (when using defaults). > bq. Error CREATEing SolrCore 'new_core': Unable to create core \[new_core\] > Caused by: Can't find resource 'solrconfig.xml' in classpath or > '/lucene-solr/solr/server/solr/new_core/conf' > The only way to get it to work would be to use the /server/<configset> > directory to be the instance directory and then, the core creation would > create unwanted directories in there. The only way to clean that up being, > {code} > > rm -rf .. ; svn up # (if it's a repo check out). > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org