Return-Path: Delivered-To: apmail-lucene-dev-archive@www.apache.org Received: (qmail 848 invoked from network); 18 Apr 2011 17:36:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 18 Apr 2011 17:36:11 -0000 Received: (qmail 79543 invoked by uid 500); 18 Apr 2011 17:36:10 -0000 Delivered-To: apmail-lucene-dev-archive@lucene.apache.org Received: (qmail 79502 invoked by uid 500); 18 Apr 2011 17:36:10 -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 Delivered-To: moderator for dev@lucene.apache.org Received: (qmail 14757 invoked by uid 99); 18 Apr 2011 16:35:57 -0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of rassahah@googlemail.com designates 209.85.212.180 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=tudQtuEDEB2vWkBD6YAzOMALb97pQ4IXTQ2OvEyWlGI=; b=PeHLepXMwkid8qJiqhcjjl8q7WShCSnBKVSpIVrbO6ga3R/pDMQWgQxbL0rARJdWLq STqNt2rMr4jIp11yiV7FG1SJ+jNEc6VYN9Ejj+EeQJ+KFb3REvXD4K3rwvaV2oLYIOVp lR+gIQYbGBkJWZOnykEOF7PDbpTptSzGWLFf4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=iN1c09L+2l5FLEjhn90GAUqFn/XNEnPkjk2wUTtWBqNVCsdCyWzBZOtjtWeyQEJAUJ mab+ds2Vr0NeRN3CrbLYkMW6La/ndG2UP7SwfxQgugDMgEuhY2lLsu3Fo+L4sFOA2Yw7 XwwmOlKy7d69vnz5rmKu/JVwS1KJcbuhxvOlw= MIME-Version: 1.0 Date: Mon, 18 Apr 2011 18:35:31 +0200 Message-ID: Subject: solr-3.1.0 bug/multicore From: Rasmus Hahn To: dev@lucene.apache.org Content-Type: text/plain; charset=ISO-8859-1 Good Morning, i noticed a small bug in your solr-3.1.0 release, but before you read any further: This should really be a bug report, but i could not find any possibility to submit a bug report into the jira (https://issues.apache.org/jira/browse/SOLR). If the latter should be possible, and someone can point me to a tutorial (best with screenshots) on where to report bugs, do not hesitate and give me a pointer. Otherwise: Phenomenon: in a multicore solr, when using the RENAME-action for two cores, and a solr.xml with persistent='true', the renamed core, does not get its name persisted in solr.xml; the old name is stored (only the solr.xml file is wrong, the in-memory-cache is correct). Reason: in org/apache/solr/core/CoreContainer.java, when persisting the CoreContainer, solr-3.1.0 writes the values of the private cores-map (solr-1.4.1 wrote the keys, too). To get the name of the core, the core's CoreDescriptor is used, but for a RENAME, the core's descriptor is not being updated. Fix: i changed this in the register-function of the CoreContainer class, since it is similar to the SWAP-operation that does a similar thing. Patch: (against https://svn.apache.org/repos/asf/lucene/dev/branches/lucene_solr_3_1) Index: solr/src/java/org/apache/solr/core/CoreContainer.java =================================================================== --- solr/src/java/org/apache/solr/core/CoreContainer.java (revision 1094545) +++ solr/src/java/org/apache/solr/core/CoreContainer.java (working copy) @@ -381,7 +381,12 @@ SolrCore old = null; synchronized (cores) { old = cores.put(name, core); + /* + * set both the name of the descriptor and the name of the + * core, since the descriptors name is used for persisting. + */ core.setName(name); + core.getCoreDescriptor ().name = name; } Best Regards - Rasmus --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org