Re: Lucene refresh index function (incremental indexing).
Hi, It's not clear what you mean when you say refresh indexes or re-compiling. If you're adding new documents just use the add() method. If you are replacing documents, you need to first delete the old ones and then add them again. Look at the mailing list archive for this, since it's been discussed several times. On Sun, Nov 23, 2003 at 12:22:40AM +0800, Tun Lin wrote: Hi, I am new here. May I know how to refresh indexes in Lucene immediately after new documents have been added without re-compiling again to reindex the documents in that particular directory? Thanks. -- Dror Matalon Zapatec Inc 1700 MLK Way Berkeley, CA 94709 http://www.fastbuzz.com http://www.zapatec.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Dates and others
Hi guys - First off I want to just give the Lucene project credit for producing an API like this. Truly great stuff. I was just wondering if anyone could share some wisdom on a couple of issues: 1. The power of dates: I am fairly happy with the results of queries on my index. The only issue I have is that at the moment the date of the content isn't considered (since lucene doesn't know about it). Is there a good way in which the date of the content could be used to help with the scoring? So more recent content shows up higher in the stack. I have a date keyword field, but it isn't part of the query itself. Are there any patterns to help with this? 2. +field:foo and the QueryParser: I ran into some problems where using +field:foo was giving strange results. When I changed the queries to ... AND field:foo everything was fine. Am I missing something there? 3. I have some fields suck as title, owner, etc as well as the content blob which I index and use as the default search field. Is there an easy way to extend the QueryParser to merge it with a MultiTermQuery which can also search this meta data and give them certain weights? Or, if you go down this path do you have to leave the QueryParser behind and build your own queries? Any best practices would be great. Sorry for bugging the list. Cheers, Dion - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
