lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erik Hatcher <>
Subject Re: Design question [too many fields?]
Date Wed, 29 Jun 2005 14:03:06 GMT
I second Mark's suggestion over the alternative I posted.  My  
alternative was merely to invert the field structure originally  
described, but using a Filter for the volatile information is wiser.


On Jun 29, 2005, at 9:58 AM, mark harwood wrote:

> Presumably there is also a free-text element to the
> search or you wouldn't be using Lucene.
> Multiple fields is not the way to go.
> A single Lucene field could contain multiple terms (
> the available dates) but I still don't think that's
> the best solution.
> The availability info is likely to be pretty volatile
> and you always want up-to-date info so I would prefer
> to hit a database for this. If you keep a DB primary
> key to Lucene doc id look-up cached in memory you can
> quickly construct a Lucene filter from the database
> results and therefore only show Lucene results for
> available rooms.
> Cheers
> Mark
> ___________________________________________________________
> How much free photo storage do you get? Store your holiday
> snaps for FREE with Yahoo! Photos
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message