Return-Path: X-Original-To: apmail-lucene-java-user-archive@www.apache.org Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 56D1698F5 for ; Wed, 25 Jan 2012 22:08:34 +0000 (UTC) Received: (qmail 90003 invoked by uid 500); 25 Jan 2012 22:08:32 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 89907 invoked by uid 500); 25 Jan 2012 22:08:31 -0000 Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-user@lucene.apache.org Delivered-To: mailing list java-user@lucene.apache.org Received: (qmail 89899 invoked by uid 99); 25 Jan 2012 22:08:30 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Jan 2012 22:08:30 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.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; Wed, 25 Jan 2012 22:08:25 +0000 Received: by obcwp18 with SMTP id wp18so8933274obc.35 for ; Wed, 25 Jan 2012 14:08:04 -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:content-type:content-transfer-encoding; bh=xEBV/3ZIDkHXPAnx+ONjbD5nxJGQxAprAYUKyuAnK1Q=; b=tw16IHTa8S+7Pvaw1VD1jZA0K2QGrNVxuUT4ragaalwP3ojxnuHSAXh+KpbjO+NIgv CuKtnsZ7cB5UwOCGNVGVgV9Rn9i5P4bPUDJTXon4GegGnq2332D1U+6MyNZ9XYA7LTLg zp9fIOATvOlVmzeP30lvVidCUV+VzxYuWQgLk= MIME-Version: 1.0 Received: by 10.182.160.1 with SMTP id xg1mr17350268obb.30.1327529284182; Wed, 25 Jan 2012 14:08:04 -0800 (PST) Received: by 10.60.78.170 with HTTP; Wed, 25 Jan 2012 14:08:04 -0800 (PST) Reply-To: simon.willnauer@gmail.com In-Reply-To: <69C3E7DDF0760840807F5FBADDD40C3E170AC8C5@sm-ex-02-vm.guidewire.com> References: <69C3E7DDF0760840807F5FBADDD40C3E170AC8C5@sm-ex-02-vm.guidewire.com> Date: Wed, 25 Jan 2012 23:08:04 +0100 Message-ID: Subject: Re: Multiple document types From: Simon Willnauer To: java-user Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org 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 wrot= e: > 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 multi= ple documents on solr? Do I need to have one webapp instance per document t= ype? For example, if I am deploying under tomcat, do I need to have a separ= ate webapps each with its own context-path and set of config files (data-co= nfig.xml and schema.xml, in particular)? > > _________________________________________ > Frank DeRose > Guidewire Software | Senior Software Engineer > Cell: 510 -589-0752 > fderose@guidewire.com | 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