Return-Path: Delivered-To: apmail-lucene-solr-commits-archive@minotaur.apache.org Received: (qmail 48133 invoked from network); 29 Jun 2009 21:30:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 29 Jun 2009 21:30:10 -0000 Received: (qmail 24192 invoked by uid 500); 29 Jun 2009 21:30:20 -0000 Delivered-To: apmail-lucene-solr-commits-archive@lucene.apache.org Received: (qmail 24101 invoked by uid 500); 29 Jun 2009 21:30:20 -0000 Mailing-List: contact solr-commits-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-dev@lucene.apache.org Delivered-To: mailing list solr-commits@lucene.apache.org Received: (qmail 24092 invoked by uid 99); 29 Jun 2009 21:30:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Jun 2009 21:30:20 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.130] (HELO eos.apache.org) (140.211.11.130) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 29 Jun 2009 21:30:17 +0000 Received: from eos.apache.org (localhost [127.0.0.1]) by eos.apache.org (Postfix) with ESMTP id 7F106118AE for ; Mon, 29 Jun 2009 21:29:56 +0000 (GMT) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Apache Wiki To: solr-commits@lucene.apache.org Date: Mon, 29 Jun 2009 21:29:56 -0000 Message-ID: <20090629212956.9860.42938@eos.apache.org> Subject: [Solr Wiki] Trivial Update of "CoreAdmin" by MarkBennett X-Virus-Checked: Checked by ClamAV on apache.org Dear Wiki user, You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification. The following page has been changed by MarkBennett: http://wiki.apache.org/solr/CoreAdmin ------------------------------------------------------------------------------ = Quick Review: What are Multiple Cores? = - Multiple cores let you have separate configurations and indexes, with their own config and schema for very different applications, but still have the convenience of unified administration. Individual indexes are still fairly isolated, but you can manage them as a single application, create new indexes on the fly by spinning up new !SolrCores, and even make one !SolrCore replace another !SolrCore without ever restarting your Servlet Container. See ["MultipleIndexes"] + Multiple cores let you have a single Solr instance with separate configurations and indexes, with their own config and schema for very different applications, but still have the convenience of unified administration. Individual indexes are still fairly isolated, but you can manage them as a single application, create new indexes on the fly by spinning up new !SolrCores, and even make one !SolrCore replace another !SolrCore without ever restarting your Servlet Container. See ["MultipleIndexes"] = Core Administration =