lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lance Norskog <goks...@gmail.com>
Subject Re: Storing different entities in Solr
Date Sat, 29 May 2010 01:08:37 GMT
The size of the join table is the number of documents, if you
denormalize the two tables.

On Fri, May 28, 2010 at 11:38 AM, Nagelberg, Kallin
<KNagelberg@globeandmail.com> wrote:
> I agree with Erick,
>
> Could you show us what these two entities look like, and the total count of each? That
might shed some light on the appropriate approach.
>
> -Kallin Nagelberg
>
> -----Original Message-----
> From: Erick Erickson [mailto:erickerickson@gmail.com]
> Sent: Friday, May 28, 2010 2:36 PM
> To: solr-user@lucene.apache.org
> Subject: Re: Storing different entities in Solr
>
> 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.
>> >>
>> >
>>
>



-- 
Lance Norskog
goksron@gmail.com

Mime
View raw message