Message-
From: Chris Lu [mailto:[EMAIL PROTECTED]
Sent: Friday, October 06, 2006 2:52 PM
To: java-user@lucene.apache.org
Subject: Re: Design Consideration for lucene index
Regarding Question #1:
If there is only Keyword matching for tags, you can achieve the same
by creating a table with two
The mantra I tell people when they are trying to decide how to index their
"relational" data is to start by asking yourself what you want the results
to be.
Is the primary list of "things" you want to return to your clients a list
of "tags" or a list of "images" ... It's not clear to me what the
Regarding Question #1:
If there is only Keyword matching for tags, you can achieve the same
by creating a table with two fields like this: (one tag, a list of
images) in database to mimic Erick's answer. No lucene really needed
for this case. Of course this would not help if you want to search
sev
, 2006 12:34 PM
To: java-user@lucene.apache.org
Subject: Re: Design Consideration for lucene index
If you're *sure* that your database solution isn't adequate see
below.
On 10/6/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> I am a newbie to the lucene search area
If you're *sure* that your database solution isn't adequate see
below.
On 10/6/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I am a newbie to the lucene search area. I would like to best way to do
the following using lucene in terms of efficiency and the size of the
index.
Question : #
