Hey Iam, I have worked on the approach number 3 recently. It suits our requirement although its not the best way to do incremental updates. Please find the details here <http://the10minutes.blogspot.com/2010/10/lucene-index-update.html>
Nilesh On Mon, Nov 1, 2010 at 12:25 PM, Iam Jabour <iamjab...@gmail.com> wrote: > Hi, I use Lucene to index my documents and search. Actually I have > 800k documents indexed in Lucene. Those documents have some fields: > > Id: is a Numeric field to index the documents > > Name: is a textual field to be stored and analyzed > > Description: like name > > Availability: is a numeric field to filter results. This field can be > updated frequently, every day. > > My question is: What's the better way to create a filter for availability? > > 1 - add this information to index and make a lucene filter. With this > approach I have to update document (remove and add, because lucene > 3.0.2 not have update support) every time the "availability" changes. > What the cost of reindex? > > 2 - don't add this information to index, and filter the results with a > DB select. This approach will do a lot of selects, because I need > select every id from database to check availability. > > 3 - Create a separated index with id and availability. I don't know if > it is a good solution, but I can create a index with static > information and other with information can be frequently updated. I > think it is better then update all document, just because some fields > were updated. > > ______________ > Iam Jabour > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > >
