Return-Path: 
 <solr-user-return-62453-apmail-lucene-solr-user-archive=lucene.apache.org@lucene.apache.org>
X-Original-To: apmail-lucene-solr-user-archive@minotaur.apache.org
Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 4404498E2
	for <apmail-lucene-solr-user-archive@minotaur.apache.org>;
 Thu, 26 Jan 2012 08:00:00 +0000 (UTC)
Received: (qmail 74419 invoked by uid 500); 26 Jan 2012 07:59:50 -0000
Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org
Received: (qmail 74048 invoked by uid 500); 26 Jan 2012 07:59:42 -0000
Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:solr-user-help@lucene.apache.org>
List-Unsubscribe: <mailto:solr-user-unsubscribe@lucene.apache.org>
List-Post: <mailto:solr-user@lucene.apache.org>
List-Id: <solr-user.lucene.apache.org>
Reply-To: solr-user@lucene.apache.org
Delivered-To: mailing list solr-user@lucene.apache.org
Received: (qmail 74030 invoked by uid 99); 26 Jan 2012 07:59:38 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Jan 2012 07:59:38 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=HS_INDEX_PARAM,NORMAL_HTTP_TO_IP,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of
 simon.willnauer@googlemail.com designates 209.85.214.176 as permitted sender)
Received: from [209.85.214.176] (HELO mail-tul01m020-f176.google.com)
 (209.85.214.176)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Jan 2012 07:59:32 +0000
Received: by obcwp18 with SMTP id wp18so363655obc.35
        for <multiple recipients>; Wed, 25 Jan 2012 23:59:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlemail.com; s=gamma;
        h=mime-version:reply-to:in-reply-to:references:date:message-id
         :subject:from:to:cc:content-type:content-transfer-encoding;
        bh=ddVNY1us9ab0+Ps2lR3D9yFpm32TMCL5PZwd2n6CMeI=;
        b=fhxkmqTXzXXYyQ6xQ8xO3A2tnYzcaew17UpLntOIKsIW3QfoY+CcqC1gk8c2SPPWDU
         JsWzM4DQCnsMrIVL/Y2v5NhSCCnpwkAb2YiaPd02cENq67QJ8gsYdLzdXTCOG93QeVyS
         pOfpFQ4ybFmWlDBBem6Yp7zCVFk2y89mcDHf0=
MIME-Version: 1.0
Received: by 10.182.160.65 with SMTP id xi1mr1152728obb.40.1327564752142; Wed,
 25 Jan 2012 23:59:12 -0800 (PST)
Received: by 10.60.78.170 with HTTP; Wed, 25 Jan 2012 23:59:12 -0800 (PST)
Reply-To: simon.willnauer@gmail.com
In-Reply-To: 
 <69C3E7DDF0760840807F5FBADDD40C3E170AC911@sm-ex-02-vm.guidewire.com>
References: 
 <69C3E7DDF0760840807F5FBADDD40C3E170AC8C5@sm-ex-02-vm.guidewire.com>
	<CAAHmpkgjQ_BTxi1M941eufPrEwORyRv-seh3VQTUjyitW5ZtOA@mail.gmail.com>
	<69C3E7DDF0760840807F5FBADDD40C3E170AC911@sm-ex-02-vm.guidewire.com>
Date: Thu, 26 Jan 2012 08:59:12 +0100
Message-ID: 
 <CAAHmpkgoiMStWUT64FEjbsKurzuX-Ywmo-Bw3FXZrWmY9gc10Q@mail.gmail.com>
Subject: Re: Multiple document types
From: Simon Willnauer <simon.willnauer@googlemail.com>
To: Frank DeRose <fderose@guidewire.com>
Cc: "java-user@lucene.apache.org" <java-user@lucene.apache.org>,
	"solr-user@lucene.apache.org" <solr-user@lucene.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Thu, Jan 26, 2012 at 12:05 AM, Frank DeRose <fderose@guidewire.com> wrot=
e:
> Hi Simon,
>
> No, not different entity types, but actually different document types (I =
think). What would be ideal is if we could have multiple <document> element=
s in the data-config.xml file and some way of mapping each different <docum=
ent> element to a different sets of field in the schema.xml file, and to a =
different index. Then, when Solr got a search request on one url (say, for =
example, "http://172.24.1.16:8080/gwsolr/cc/doctype1/select/?q=3D..."), it =
would search for a document in the first index and when it got a search req=
uest on a different url (say, for example, "http://172.24.1.16:8080/gwsolr/=
pc/doctype1/select/?q=3D..."), it would search for the document in the seco=
nd index. In like manner, administrative tasks (like dataimport) would also=
 switch off of the url, so that the url would determine which index was to =
be loaded by the dataimport command.

seems like you should look at solr's multicore feature:
http://wiki.apache.org/solr/CoreAdmin

simon
>
> F
>
> -----Original Message-----
> From: Simon Willnauer [mailto:simon.willnauer@googlemail.com]
> Sent: Wednesday, January 25, 2012 2:08 PM
> To: java-user
> Subject: Re: Multiple document types
>
> hey Frank,
>
> can you elaborate what you mean by different doc types? Are you
> referring to an entity ie. a table per entity to speak in SQL terms?
> in general you should get better responses for solr related questions
> on solr-user@lucene.apache.org
>
> simon
>
> On Wed, Jan 25, 2012 at 10:49 PM, Frank DeRose <fderose@guidewire.com> wr=
ote:
>> It seems that it is not possible to have multiple document types defined=
 in a single solr schema.xml file. If, in fact, this is not possible, then,=
 what is the recommended app server deployment strategy for supporting mult=
iple documents on solr? Do I need to have one webapp instance per document =
type? For example, if I am deploying under tomcat, do I need to have a sepa=
rate webapps each with its own context-path and set of config files (data-c=
onfig.xml and schema.xml, in particular)?
>>
>> _________________________________________
>> Frank DeRose
>> Guidewire Software | Senior Software Engineer
>> Cell: 510 -589-0752
>> fderose@guidewire.com<mailto:fderose@guidewire.com> | www.guidewire.com<=
http://www.guidewire.com/>
>> Deliver insurance your way with flexible core systems from Guidewire.
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>