lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erick Erickson" <>
Subject Re: Does lucene performance suffer with a lot of empty fields ?
Date Tue, 01 Aug 2006 13:10:25 GMT
I can't speak to performance, but there's no problem having different fields
for different documents. Stated differently, you don't need to have all
fields in all documents. It took me a while to get my head out of database
tables and accept this <G>....

I doubt there's a problem with speed, but as always some measurements over
your particular data count most.....


On 8/1/06, Mek <> wrote:
> I have 1 generic index, but am Indexing a lot of different things, like
> actors, politicians, scientists, sportsmen.
> And as you can see that though there are some common fields, like name &
> DOB, there are also fields for each of these types of people that are
> different.
> e.g. Actors will have "Movies, TV shows, ", politicians will have
> "Political
> party...", scientists will have "publications, inventions ..."
> Also, I do not want to create multiple indexes, as the number of such
> types
> & hence the number of indices can get out of hand, eg I could decide to
> add
> "footballers", "tennis players".
> I am sure I am not the 1st who's facing this problem.
> From what I gather, I can go ahead & create an Index & for each Document &
> only add the relevant fields. Is this correct?
> I should still be able to search with queries like "mel
> Movies:braveheart".
> Right ?
> Would this impact the search performance ?
> Any other words of caution for me ?
> Thanks,
> mek

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message