From dev-return-310400-archive-asf-public=cust-asf.ponee.io@lucene.apache.org Thu Feb 1 17:51:05 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id 7E169180652 for ; Thu, 1 Feb 2018 17:51:05 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 6E426160C57; Thu, 1 Feb 2018 16:51:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B4D3D160C44 for ; Thu, 1 Feb 2018 17:51:04 +0100 (CET) Received: (qmail 79135 invoked by uid 500); 1 Feb 2018 16:51:03 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 79113 invoked by uid 99); 1 Feb 2018 16:51:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Feb 2018 16:51:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id D91F81A67C6 for ; Thu, 1 Feb 2018 16:51:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -102.311 X-Spam-Level: X-Spam-Status: No, score=-102.311 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id wrj5ylbyNJUh for ; Thu, 1 Feb 2018 16:51:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 8DD685FB76 for ; Thu, 1 Feb 2018 16:51:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id D7643E0254 for ; Thu, 1 Feb 2018 16:51:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 9561E21E83 for ; Thu, 1 Feb 2018 16:51:00 +0000 (UTC) Date: Thu, 1 Feb 2018 16:51:00 +0000 (UTC) From: "Cassandra Targett (JIRA)" To: dev@lucene.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (SOLR-11663) CLONE - API to create a core is broken MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SOLR-11663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 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: https://issues.apache.org/jira/browse/SOLR-11663 > 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|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 (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org