Thanks for reply. Generally good idea and I like it - almost :) We just need to tweak it a little more. What if I have to search for both fields at the same time? Is there any way to do something similiar to SQL JOIN on the two documents / indexes? (I don't think so) I think cascading queries will not work (first one can return large result set, so the second query could grow to large size).
>> -----Original Message----- >> From: Wojciech Strzałka [mailto:[EMAIL PROTECTED] >> Sent: den 12 september 2008 13:58 >> To: java-user@lucene.apache.org >> Subject: Frequently updated fields >> >> Hi. >> >> I'm new to Lucene and I would like to get a few answers (they can >> be lame) >> >> I want to index large amount of emails using Lucene (maybe >> SOLR), not only >> the contents but also some metadata like state or flags. The >> problem is that the metadata will change during mail lifecycle, >> although much smaller updating this information will require >> reindex the whole mail content which I see performance bottleneck. >> >> I have the data in DB also so my first question is: >> >> - are there any best practices to implement my needs (querying both >> lucene & DB and then merging in memory?, close one eye and re-index >> the whole content on every metadata change? others?) > Maybe two separate Lucene indexes? Then you can have the data not > changed often in one index, and all other data in the other index. > Or splitting one single mail into multiple documents, in the same regard. > /Jimi > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- Pozdrowienia, Wojciech Strzałka --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
