lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cassandra Targett (JIRA)" <>
Subject [jira] [Resolved] (SOLR-11663) CLONE - API to create a core is broken
Date Thu, 01 Feb 2018 16:51:00 GMT


Cassandra Targett resolved SOLR-11663.
    Resolution: Duplicate

I'm closing this as a duplicate of SOLR-7316, which was the issue this was cloned from. Since
the original is not closed, only stalled, creating a new issue doesn't do anything to push
the original issue forward.

> CLONE - API to create a core is broken
> --------------------------------------
>                 Key: SOLR-11663
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 6.6
>            Reporter: Jaya Naga Bhavana
>            Priority: Major
> *Steps To Reproduce*
> {code}
> curl 'http://localhost:8983/solr/admin/cores?action=CREATE&name=new_core&instanceDir=new_core'
> {code}
> *Expected Result*
> Create a core called "new_core".
> *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|]?
> 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}
> *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?* I'm speechless.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message