t as great as the code. :-)
Regards,
Michael
> -Ursprüngliche Nachricht-
> Von: Erick Erickson [mailto:[EMAIL PROTECTED]
> Gesendet: Donnerstag, 28. Juni 2007 20:45
> An: java-user@lucene.apache.org
> Betreff: Re: Searching over multiple indexes with 1:m relationship
>
Michael
> -Ursprüngliche Nachricht-
> Von: Erick Erickson [mailto:[EMAIL PROTECTED]
> Gesendet: Donnerstag, 28. Juni 2007 16:09
> An: java-user@lucene.apache.org
> Betreff: Re: Searching over multiple indexes with 1:m relationship
>
>
> I do have an off-the-wall ques
What you should do is denorm the 1:m relationships.
Don't try to mimic the database. If you need to, you can keep the original 2
indexes and create a third one.
--
Chris Lu
-
Instant Scalable Full-Text Search On Any Database/Application
site: http://www.dbsight.net
demo:
stag, 28. Juni 2007 16:09
> An: java-user@lucene.apache.org
> Betreff: Re: Searching over multiple indexes with 1:m relationship
>
>
> I do have an off-the-wall question.. Why have two indexes? There
> are, of course, good reasons, but they're things like size and speed.
>
I do have an off-the-wall question.. Why have two indexes? There
are, of course, good reasons, but they're things like size and speed.
Where I'm going here is that Lucene does NOT require that all
documents have the same fields. So it's perfectly reasonable to index
heterogeneous data (or differi
Hi folks!
I know there is a MultiSearcher for searching over multiple indices, but my
requirement is a bit special.
I have two indices whose documents have a 1:m relationship. Most queries
will only use the primary index, but some will have to look for detailed
information in the secondary index (
