Optimising the lucene search

[su...@zapak.co.in]

Hello,

Optimising the lucene search

Use combined search field for all text fields instead (or on the top) of
indexing them separately and searching with complex query like
field1:query OR field2:query ... OR fieldN:query

Reducing number of field make indexing and search much faster. Use
combined field instead or on the top of separate fields if needed


Does that mean that while defining structure of lucene doc ,fields (key-val)
should be in the form of

field1_field2:val1_val2
(combining fields at time of indexing itself)

instead of
field1:val1 and field2:val2

for making the search faster


Let me know for both the cases..
CASE 1: field1 and field2 are not related to each other in any ways
CASE 2: field1:field2 is having 1:n relation
eg student : frnds (where student ABC can  have 5 diff frnds)


thanks,
Suman

Ps:http://it-stream.blogspot.com/2007/12/full-text-search-for-database-using.html




---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org

Re: Optimising the lucene search

[Anshum <an...@gmail.com>]

Hi,

I couldn't really get the point here. Do you think you would never have to
search the fields separately? Concatenating the fields would mean a lot of
information loss and you'd not be able to search the fields for a query like
(Field1:X AND Field2:Y ) . If that's the case you could combine the fields
at run time.
As far as relational nature is concerned, I'd say lucene's model is pretty
different from what you're taking it to be. Lucene documents are just a
collection of field/value pairs.

--
Anshum Gupta
Naukri Labs!
http://ai-cafe.blogspot.com

The facts expressed here belong to everybody, the opinions to me. The
distinction is yours to draw............


On Tue, Mar 23, 2010 at 12:31 PM, <su...@zapak.co.in> wrote:

>
>
> Hello,
>
> Optimising the lucene search
>
> Use combined search field for all text fields instead (or on the top) of
> indexing them separately and searching with complex query like
> field1:query OR field2:query ... OR fieldN:query
>
> Reducing number of field make indexing and search much faster. Use
> combined field instead or on the top of separate fields if needed
>
>
> Does that mean that while defining structure of lucene doc ,fields
> (key-val)
> should be in the form of
>
> field1_field2:val1_val2
> (combining fields at time of indexing itself)
>
> instead of
> field1:val1 and field2:val2
>
> for making the search faster
>
>
> Let me know for both the cases..
> CASE 1: field1 and field2 are not related to each other in any ways
> CASE 2: field1:field2 is having 1:n relation
> eg student : frnds (where student ABC can  have 5 diff frnds)
>
>
> thanks,
> Suman
>
> Ps:
> http://it-stream.blogspot.com/2007/12/full-text-search-for-database-using.html
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>
>