[
https://issues.apache.org/jira/browse/SOLR-6767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14218895#comment-14218895
]
Erick Erickson commented on SOLR-6767:
--------------------------------------
+1 to adding support for configsets in the admin UI.
That said, though, when starting Solr up from scratch:
bin/solr start -e techproducts
starts up a Solr, creates a core called "techproducts" _and_ indexes the sample
docs. So perhaps we could call this out more explicitly in the docs?
I've been tripping over trying to do things that I used to do before the
directories were restructured and being surprised, only to discover that
there's usually a new way to do what I want.
I'm soooo glad that the default "collection1" is gone and that we're
introducing people to how things work re: collections/cores and creating them
though.
"It's not the things you don't know that'll kill ya, it's the things you _do_
know that ain't so" ;)
> 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: [email protected]
For additional commands, e-mail: [email protected]
