Indexing floating point number

Hi, Newbie question. How do we index floating point number in Lucene, so that it is sortable ? There is a built-in utility class 'NumberTools' which help with indexing integer. Does Lucene has the same mechanism for floating point number? Thanks.

How do I obtain the document id in order to delete from index?

Hi, I've been reading Lucene documentation and I see there are two ways of deleting a document from an index: by id and by term. Supose I have an index with three fields: field1, field2 and field3, and I want to delete all documents with field1=value1 and field2=value2. I think I must use

Re: How do I obtain the document id in order to delete from index?

I think I found it. I must do a query an then loop through the hits to obtain the id with hit.id(int n). If anyone knows any better way... Thanks - Original Message - From: Enrique Lamas [EMAIL PROTECTED] To: java-user@lucene.apache.org Sent: Monday, October 30, 2006 11:39 AM

Re: Lucene search priorities

I think what you want is IndexSearcher.search(Query, Filter, Sort). Filter may be null, and Sort is a Sort object that allows you to sort on multiple fields at once, which I assume is what you mane by priorities. Read the cautions about memory usage for a Sort object though. Best Erick On

Re: Lucene search priorities

Hi Erick, Thanks for the reply. Actually the priorities mean when i search for example for cancer then in the result if get the result in order like 1. it appears in title 2. it appears in keywords 3. it appears in synonyms. But right now with the default implementation when i search for

Re: Lucene search priorities

I don't remember the syntax right now, but how about giving a boost to certain fields, either while indexing or while searching ? Patrick On 10/30/06, Amit Soni [EMAIL PROTECTED] wrote: Hi Erick, Thanks for the reply. Actually the priorities mean when i search for example for cancer then in

Re: Lucene search priorities

Hi amit, You can give boost to query at search time... and you can boost to perticular field at index time - Bhavin pandya - Original Message - From: Patrick Turcotte [EMAIL PROTECTED] To: java-user@lucene.apache.org; [EMAIL PROTECTED] Sent: Monday, October 30, 2006 7:38 PM

Re: Announcement: Lucene powering Monster job search index (Beta)

Otis, The Lucene components for this beta are running on 4 dual core AMD Opteron ( 2.6GHZ) processors, for a total of 8 CPUs. It has 32GB RAM, although 16GB would probably suffice. The query rate is currently quite low probably because of the low visibility of the beta page. We haven't measured

Re: Announcement: Lucene powering Monster job search index (Beta)

Alex, I like your suggestion (I've found myself wondering what the last search was, too), and I've forwarded it to the UI developer. Thanks, Peter On 10/29/06, Alexandru Popescu [EMAIL PROTECTED] wrote: Peter it looks impressive. Congrats! A small suggestion, though, after performing a

Re: Announcement: Lucene powering Monster job search index (Beta)

Hi Peter, On Fri, 2006-10-27 at 15:29 -0400, Peter Keegan wrote: Numeric range search is one of Lucene's weak points (performance-wise) so we have implemented this with a custom HitCollector and an extension to the Lucene index files that stores the numeric field values for all documents.

Re: Announcement: Lucene powering Monster job search index (Beta)

Peter, Congratulation on the beta launch :) If you dont mind, I would like to ask you more on the feature 4. Sort by Miles. When you search by 4. Sort by Miles, I suppose the sorting by relevance (of the search keyword) is lost? Since this is implemented using a custom SortComparatorSource.

Re: Announcement: Lucene powering Monster job search index (Beta)

Joe, Fields with numeric values are stored in a separate file as binary values in an internal format. Lucene is unaware of this file and unaware of the range expression in the query. The range expression is parsed outside of Lucene and used in a custom HitCollector to filter out documents that

Re: Announcement: Lucene powering Monster job search index (Beta)

KEGan, When you search by 4. Sort by Miles, I suppose the sorting by relevance (of the search keyword) is lost? Since this is implemented using a custom SortComparatorSource. Sorting by miles becomes the primary sort key, score and date become secondary sort fields (in the case of ties).

Re: Indexing floating point number

On 10/30/06, KEGan [EMAIL PROTECTED] wrote: Newbie question. How do we index floating point number in Lucene, so that it is sortable ? There is a built-in utility class 'NumberTools' which help with indexing integer. Does Lucene has the same mechanism for floating point number? You can look at

FSDirectory.close()

All, Just a quick question regarding the need to call Directory.close() (actually for an FSDirectory) and whether it is really necessary. As far as I can tell, the only implication of this is that the refCount is not decremented and therefore the FSDirectory will persist for the life of the

Re: Lucene search priorities

Hi Bhavin, Thanks a lot for your reply. But i am little confuse this time. Do i have to give boost and index and search both or either index or search? Also can you give some docs which has something on how to use boost on particular fields. Thanks, Amit Soni Bhavin Pandya wrote: Hi amit,