Re: search in all fields

Here is my experience of getting a good search relevancy: pre processing is paramount. Pre process your data and using perl is much powerful and flexible then putting all the logic in a customized analyzer. And if you want to search multiple fields, create a field called "all" and cat all the

Re: Searching/indexing date/time values or numeric values?

ultimately, everything is text search. For decimal number, what you do is to write a customized analyzer which multiple the number by some factor, round it to a long and then use NumberTools to convert that into a text string. Here is what I did for latitude/longitude search: multiple it by 10

rangequery not tokenizer

It seems that range query is not going through tokenization process. E.g.: I have a field call "iso" which contains the photographic iso number such as 100, 200, 400, ... I have a special tokenizer that convert the integer using lucene's NumberTools.longToString. If I search "iso:100" everyth

efficient ways of updating document

It seems to me that updating a document is rather tedious and slow in lucene, especially for updating large number of documents. Before opening an IndexWriter to add documents, one has to open an IndexReader/IndexSearcher to search for the document of a particular id. Upon finding its docnum,

how to define deault fields

Hi: How to define default fields? Is it done during index time or during search time? Strangely, I can't find out any information on how default fields are defined? thanks, john __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best sp