Bit late joining in but since this is the first Google hit for
"site:www.nabble.com joins lucene" thought it was reasonable place to add
this note:
In my application "joins" also start to seem appealing. Almost all my use
cases fit very nicely within what Lucene does apart from a "nice to have" a
Sachin,
As the merging of the results is the issue, I'll assume that you don't
have clear user requirements for that.
The simplest way out of that is to allow the users to search
the B's first, and once they have determined which B's they'd like
to use, use those B's to limit the results in of us
Here are more details about my issue.
I have two tables in database. A row in table 1 can have multiple rows
associated with it in table 2. It is a one to many mapping.
Let's say a row in table 1 is A and it has multiple rows B1, B2 and B3
associated with it in table 2. I need to search on both A
Hi, Sachin,
If you like self-join, you may need to retrieve the data from the
second query and merge them into each Document object. Then you can do
the query in one shot. (it's redundant. but do not try to normalize
data in the index.)
Lucene is an index. Just like index in SQL database, which c
It's often a mistake to try to force Lucene to act like a database. Is it
possible to just use the database for the join portion and Lucene
for the text search?
Otherwise I agree with Developer Developer. You need to provide
a higher level idea of *what* it is you're trying to accomplish to get
go
Provide more details please.
Can you not use boolean query and filters if need be ?
On Jan 8, 2008 7:23 AM, sachin <[EMAIL PROTECTED]> wrote:
>
> I need to write lucene query something similar to SQL self joins.
>
> My current implementation is very primitive. I fire first query, get the
> res
