Another possibility is to do it backwards, it depends on how expensive the
SQL query is I suppose. The idea would be to go ahead and to your
SQL query *first*, then construct a Lucene Filter to use with your query
using TermDocs/TermEnum.
I'd guess (without knowing much about your problem space) t
twoch, 13. Februar 2008 18:44
> To: java-user@lucene.apache.org
> Subject: Re: design: merging resultset from RDBMS with lucene
> search results
>
> Hi,
>
> You might consider avoiding this problem altogether, by simply adding
> the meta data to your Lucene index. Lucene
Hi,
You might consider avoiding this problem altogether, by simply adding
the meta data to your Lucene index. Lucene can handle untokenized
fields, which is ideal for meta data. It might not be as quick as the
RDB, but you could perhaps optimize by only searching in the RDB when
you only need
Hi,
I have the following scenario:
RDBMS which contains the metadata for documents (ID, customer number,
doctype etc.).
Now I want to add fulltext search support.
So I will index the documents content in lucene and add the documents ID as
a stored field in lucene.
Now somebody wants to search l
