[
https://issues.apache.org/jira/browse/SOLR-7323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Haase updated SOLR-7323:
-----------------------------
Description:
*To Reproduce*
Try to create a core using Core Admin API and a config set:
{code}
curl
'http://localhost:8983/solr/admin/cores?action=CREATE&name=new_core&configSet=basic_configs'
{code}
*Expected Outcome*
Core is created in `/var/solr/data/new_core` using one of the config sets
installed by the installer script in
`/opt/solr/server/solr/configsets/basic_configs`.
*Actual Outcome*
{code}
<?xml version="1.0" encoding="UTF-8"?>
<response>
<lst name="responseHeader"><int name="status">400</int><int
name="QTime">9</int></lst><lst name="error"><str name="msg">Error CREATEing
SolrCore 'new_core': Unable to create core [new_core] Caused by: Could not load
configuration from directory /var/solr/data/configsets/basic_configs</str><int
name="code">400</int></lst>
</response>
{code}
Why is it looking for config sets in /var/solr/data? I don't know. If that's
where configsets are supposed to be placed, then why does the installer put
them somewhere else?
There's no documented API to tell it to look for config sets anywhere else,
either. It will always search inside /var/solr/data.
was:
**To Reproduce**
Try to create a core using Core Admin API and a config set:
{code}
curl
'http://localhost:8983/solr/admin/cores?action=CREATE&name=new_core&configSet=basic_configs'
{code}
**Expected Outcome**
Core is created in `/var/solr/data/new_core` using one of the config sets
installed by the installer script in
`/opt/solr/server/solr/configsets/basic_configs`.
**Actual Outcome**
{code}
<?xml version="1.0" encoding="UTF-8"?>
<response>
<lst name="responseHeader"><int name="status">400</int><int
name="QTime">9</int></lst><lst name="error"><str name="msg">Error CREATEing
SolrCore 'new_core': Unable to create core [new_core] Caused by: Could not load
configuration from directory /var/solr/data/configsets/basic_configs</str><int
name="code">400</int></lst>
</response>
{code}
Why is it looking for config sets in /var/solr/data? I don't know. If that's
where configsets are supposed to be placed, then why does the installer put
them somewhere else?
There's no documented API to tell it to look for config sets anywhere else,
either. It will always search inside /var/solr/data.
> Core Admin API looks for config sets in wrong directory
> -------------------------------------------------------
>
> Key: SOLR-7323
> URL: https://issues.apache.org/jira/browse/SOLR-7323
> Project: Solr
> Issue Type: Bug
> Affects Versions: 5.0
> Reporter: Mark Haase
>
> *To Reproduce*
> Try to create a core using Core Admin API and a config set:
> {code}
> curl
> 'http://localhost:8983/solr/admin/cores?action=CREATE&name=new_core&configSet=basic_configs'
> {code}
> *Expected Outcome*
> Core is created in `/var/solr/data/new_core` using one of the config sets
> installed by the installer script in
> `/opt/solr/server/solr/configsets/basic_configs`.
> *Actual Outcome*
> {code}
> <?xml version="1.0" encoding="UTF-8"?>
> <response>
> <lst name="responseHeader"><int name="status">400</int><int
> name="QTime">9</int></lst><lst name="error"><str name="msg">Error CREATEing
> SolrCore 'new_core': Unable to create core [new_core] Caused by: Could not
> load configuration from directory
> /var/solr/data/configsets/basic_configs</str><int name="code">400</int></lst>
> </response>
> {code}
> Why is it looking for config sets in /var/solr/data? I don't know. If that's
> where configsets are supposed to be placed, then why does the installer put
> them somewhere else?
> There's no documented API to tell it to look for config sets anywhere else,
> either. It will always search inside /var/solr/data.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
