[
https://issues.apache.org/jira/browse/SOLR-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Haase updated SOLR-7316:
-----------------------------
Description:
h1. Steps To Reproduce
{code}
curl
'http://localhost:8983/solr/admin/cores?action=CREATE&name=new_core&instanceDir=new_core'
{code}
h1. Expected Result
Create a core called "new_core".
h1. Actual Result
{quote}
Error CREATEing SolrCore 'new_core': Unable to create core [new_core] Caused
by: Can't find resource 'solrconfig.xml' in classpath or
'/var/solr/data/new_core/conf'
{quote}
Somebody on solr-users tells me:
{quote}
The CoreAdmin API requires that the instanceDir already exist, with a
conf directory inside it that contains solrconfig.xml, schema.xml, and
any other necessary config files.
{quote}
Huh? Where is this magical knowledge mentioned in the [API
documentation|https://cwiki.apache.org/confluence/display/solr/CoreAdmin+API]?
Another user on the list serve says:
{quote}
In fact, yes. The thing to remember here is that you're using a much
older approach that had its roots in the pre-cloud days.
{quote}
My response:
{quote}
>From an API consumer's point of view, I'm not really interested in being
>forced to learn the history of the project to use the API. *The whole point of
>creating APIs is to abstract out details that the caller doesn't need to know,
>and yet this API requires an understanding of Solr's internal file structure
>and history of the project?*
{quote}
(Emphasis added.)
was:
h1. Steps To Reproduce
# curl
'http://localhost:8983/solr/admin/cores?action=CREATE&name=new_core&instanceDir=new_core'
h1. Expected Result
Create a core called "new_core".
h1. Actual Result
{quote}
Error CREATEing SolrCore 'new_core': Unable to create core [new_core] Caused
by: Can't find resource 'solrconfig.xml' in classpath or
'/var/solr/data/new_core/conf'
{quote}
Somebody on solr-users tells me:
{quote}
The CoreAdmin API requires that the instanceDir already exist, with a
conf directory inside it that contains solrconfig.xml, schema.xml, and
any other necessary config files.
{quote}
Huh? Where is this magical knowledge mentioned in the [API
documentation|https://cwiki.apache.org/confluence/display/solr/CoreAdmin+API]?
Another user on the list serve says:
{quote}
In fact, yes. The thing to remember here is that you're using a much
older approach that had its roots in the pre-cloud days.
{quote}
My response:
{quote}
>From an API consumer's point of view, I'm not really interested in being
>forced to learn the history of the project to use the API. *The whole point of
>creating APIs is to abstract out details that the caller doesn't need to know,
>and yet this API requires an understanding of Solr's internal file structure
>and history of the project?*
{quote}
(Emphasis added.)
> API to create a core is broken
> ------------------------------
>
> Key: SOLR-7316
> URL: https://issues.apache.org/jira/browse/SOLR-7316
> Project: Solr
> Issue Type: Bug
> Components: Server
> Affects Versions: 5.0
> Reporter: Mark Haase
>
> h1. Steps To Reproduce
> {code}
> curl
> 'http://localhost:8983/solr/admin/cores?action=CREATE&name=new_core&instanceDir=new_core'
> {code}
> h1. Expected Result
> Create a core called "new_core".
> h1. Actual Result
> {quote}
> Error CREATEing SolrCore 'new_core': Unable to create core [new_core] Caused
> by: Can't find resource 'solrconfig.xml' in classpath or
> '/var/solr/data/new_core/conf'
> {quote}
> Somebody on solr-users tells me:
> {quote}
> The CoreAdmin API requires that the instanceDir already exist, with a
> conf directory inside it that contains solrconfig.xml, schema.xml, and
> any other necessary config files.
> {quote}
> Huh? Where is this magical knowledge mentioned in the [API
> documentation|https://cwiki.apache.org/confluence/display/solr/CoreAdmin+API]?
> Another user on the list serve says:
> {quote}
> In fact, yes. The thing to remember here is that you're using a much
> older approach that had its roots in the pre-cloud days.
> {quote}
> My response:
> {quote}
> From an API consumer's point of view, I'm not really interested in being
> forced to learn the history of the project to use the API. *The whole point
> of creating APIs is to abstract out details that the caller doesn't need to
> know, and yet this API requires an understanding of Solr's internal file
> structure and history of the project?*
> {quote}
> (Emphasis added.)
--
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
