[
https://issues.apache.org/jira/browse/SOLR-6767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14218760#comment-14218760
]
Anshum Gupta commented on SOLR-6767:
------------------------------------
The scripts work fine as they use configSet param while creating the core. Here
are 2 things that (together) might help:
1. Support specifying the configset in the admin UI.
2. Like in SolrCloud mode, copy the root server directory to another directory
(node?) and run the node off it. That would ensure that the checkout stays
clean when using the schema-less mode.
> 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
> 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: [email protected]
For additional commands, e-mail: [email protected]
