[ 
https://issues.apache.org/jira/browse/SOLR-11663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16262576#comment-16262576
 ] 

Shawn Heisey edited comment on SOLR-11663 at 11/22/17 2:15 PM:
---------------------------------------------------------------

If you want to create indexes without any access to the filesystem where Solr 
is running, then you should run SolrCloud, which requires that you set up 
zookeeper.  If you run SolrCloud, then you won't be using the CoreAdmin API, 
you'll be using the Collections API.

https://lucene.apache.org/solr/guide/6_6/collections-api.html

For standalone mode there is the configset feature, which allows configurations 
to work in a manner very close to how SolrCloud works, except that it is 
confined to one server, whereas SolrCloud can share configurations across many 
servers.

The "standard" setup with standalone Solr requires that you create the 
instanceDir and the configuration before you add a core with the CoreAdmin API.



was (Author: elyograg):
If you want to create indexes without any access to the filesystem where Solr 
is running, then you should run SolrCloud, which requires that you set up 
zookeeper.

For standalone mode there is the configset feature, which allows configurations 
to work in a manner very close to how SolrCloud works, except that it is 
confined to one server, whereas SolrCloud can share configurations across many 
servers.

The "standard" setup with standalone Solr requires that you create the 
instanceDir and the configuration before you add a core with the CoreAdmin API.


> CLONE - API to create a core is broken
> --------------------------------------
>
>                 Key: SOLR-11663
>                 URL: https://issues.apache.org/jira/browse/SOLR-11663
>             Project: Solr
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 6.6
>            Reporter: Jaya Naga Bhavana
>
> *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|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}
> *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
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to