Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of erickerickson@gmail.com
 designates 209.85.160.176 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=hyBlzJ4SesG6Vp140W8FJhmccltSggA/85/rrExftXbgTBNNkS155FKnXOceo6UBHo
         /SZKx2DGqutuEVhE0hK1rkg09LHrO3j4j//3ZURB6JriSB0nxh5YLA5267uMrun33a1s
         vS3H9AmSiBaUnPLPJ0GH1KlCN6siWELcbo1Jg=
MIME-Version: 1.0
In-Reply-To: <AANLkTinScij_49VvWdkrZNoYzXslQQr-XcndFsh9-nF6@mail.gmail.com>
References: <AANLkTilWZ6JzOFBhSnozPCDwR262i_xWzEKBvfi3S385@mail.gmail.com>
	<1275063987240-852346.post@n3.nabble.com>
	<13D828CF2C5A6D4597111B6E6571FD63090063C7A7@GMEXMBS2.globeandmail.net>
	<AANLkTimaO6vBk2twoYBjuPNnL6MrTqVhB8vHFgCloVx2@mail.gmail.com>
	<AANLkTinScij_49VvWdkrZNoYzXslQQr-XcndFsh9-nF6@mail.gmail.com>
Date: Fri, 28 May 2010 14:35:48 -0400
Message-ID: <AANLkTime5a_WJiD-upxiZtC7831KkCgbBQ41zxISdXYP@mail.gmail.com>
Subject: Re: Storing different entities in Solr
From: Erick Erickson <erickerickson@gmail.com>
To: solr-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=000e0cd56cc6a2d1990487abc65b

--000e0cd56cc6a2d1990487abc65b
Content-Type: text/plain; charset=ISO-8859-1

You most certainly *can* store the many<->many relationship, you
are just denormalizing your data. I know it goes against the grain
of any good database admin, but it's very often a good solution
for a search application.

You've gotta forget almost everything you learned about how data
*should* be stored in databases when working with a search app.
Well, perhaps I'm overstating a bit, but you get the idea....

When I see messages about primary keys and foreign keys etc, I
break out in hives. It's almost always a mistake to try to force
lucene/solr to behave like a database. Whenever you find yourself
trying, stop, take a deep breath, and think about searching <G>...

A lot depends on how much data we're talking about here. If
fully denormalizing things would cost you 10M, who cares? If it
would cost you 100G, it's a different story....

Best
Erick


On Fri, May 28, 2010 at 1:12 PM, Moazzam Khan <moazzamk@gmail.com> wrote:

> Thanks for all your answers guys. Requests and consultants have a many
> to many relationship so I can't store request info in a document with
> advisorID as the primary key.
>
> Bill's solution and multicore solutions might be what I am looking
> for. Bill, will I be able to have 2 primary keys (so I can update and
> delete documents)? If yes, can you please give me a link or someting
> where I can get more info on this?
>
> Thanks,
> Moazzam
>
>
>
> On Fri, May 28, 2010 at 11:50 AM, Bill Au <bill.w.au@gmail.com> wrote:
> > You can keep different type of documents in the same index.  If each
> > document has a type field.  You can restrict your searches to specific
> > type(s) of document by using a filter query, which is very fast and
> > efficient.
> >
> > Bill
> >
> > On Fri, May 28, 2010 at 12:28 PM, Nagelberg, Kallin <
> > KNagelberg@globeandmail.com> wrote:
> >
> >> Multi-core is an option, but keep in mind if you go that route you will
> >> need to do two searches to correlate data between the two.
> >>
> >> -Kallin Nagelberg
> >>
> >> -----Original Message-----
> >> From: Robert Zotter [mailto:robertzotter@gmail.com]
> >> Sent: Friday, May 28, 2010 12:26 PM
> >> To: solr-user@lucene.apache.org
> >> Subject: Re: Storing different entities in Solr
> >>
> >>
> >> Sounds like you'll want to use a multiple core setup. One core fore each
> >> type
> >> of "document"
> >>
> >> http://wiki.apache.org/solr/CoreAdmin
> >> --
> >> View this message in context:
> >>
> http://lucene.472066.n3.nabble.com/Storing-different-entities-in-Solr-tp852299p852346.html
> >> Sent from the Solr - User mailing list archive at Nabble.com.
> >>
> >
>

--000e0cd56cc6a2d1990487abc65b--