Re: Modelling relational data in Lucene Index?

e near 0.5 million. The cons are startup will be slow when data increase, but server shouldnt be down that often. Is anyone using similar model ? Any pitfall that I should be aware about ? Thanks. ~KEGan On 11/6/06, Emmanuel Bernard <[EMAIL PROTECTED]> wrote: I had a quick look at SOLR a

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.

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.

Re: Number Proximity Query

m not sure if I am asking the correct question :) It's 3am now. I will write more tomorrow. Good night :) ~KEGan On 10/5/06, Chris Hostetter <[EMAIL PROTECTED]> wrote: : (1) Should values returned by DocValues (return from ValueSource) must : always betwen 1.0 and 0.0 ? How is

Re: Number Proximity Query

ute to the overall document score. ~KEGan On 10/4/06, Erick Erickson <[EMAIL PROTECTED]> wrote: Sorry if this is a re-post, but I got an "undeliverable" error last time I tried to post it, something about SPAM. The nerve of that filter! I don't have my bo

Re: Number Proximity Query

n help out ? -- Weight.getValue() : what values should be returned for NumberProximityQuery? -- Weight.sumOfSquareWeights() : no idea what is this for??? -- Weight.normalize() : still no idea -- Scorer.score() : should this value always between 1.0 and 0.0 ? Thanks. ~KEGan On 10/4/06, Chris Hostett

Number Proximity Query

lso search on how to write my own query instance, but there is lack of documentation on doing so. The formula to calculate the number proximity is quite trivial. But how to stitch together Query, Weight, Scorer is the problem :( Any suggestion is greatly appreciated :) ~KEGan

Re: Sort by date THEN by relevancy

Erick, Wow!! Thanks for the invaluable advice and sharing of your experience :) I greatly appreciate them. Alright, I think it really make the most sense to follow the path of least resistant first, then see if it really need optimization. Thanks a lot. ~KEGan On 9/30/06, Erick Erickson

Re: Sort by date THEN by relevancy

ll be more searches than inserts. Is this what people normally do? Thanks. ~KEGan On 9/30/06, Erick Erickson <[EMAIL PROTECTED]> wrote: Sorting will inevitably have an impact on your speed, but it's impossible to generalize. FWIW, my app has 870K documents, the index is around 1.4G and

Re: Sort by date THEN by relevancy

Erick, Ouch!! Please excuse the cut-n-paste ;) LIA mentions a lot about performance when doing sorting. Is it something to be cautious about? You mention doing 5 fields and it works ok, ... can share with us how many documents you are handling there with 5 fields ? Thanks. ~KEGan On 9/29/06

Re: Sort by date THEN by relevancy

I think I am going to answer my own question. Just use the *Sort* (SortField [] fields) *Sort* (String <http://java.sun.com/j2se/1.4/docs/api/java/lang/String.html> [] fields) This should do it right ? On 9/29/06, KEGan <[EMAIL PROTECTED]> wrote: Hi, I have seen some sort exa

Sort by date THEN by relevancy

Hi, I have seen some sort examples in LIA. But cant find what I am looking for. How do I sort document by date, AND for all the documents with the same date ... these are sorted by relavency. (Date has higher sort priority in this case). Thanks.

Re: Lucene In Action Book vs Lucene 2.0

lish it along with LIA2. It IS coming! :) Otis ----- Original Message From: KEGan <[EMAIL PROTECTED]> To: java-user@lucene.apache.org Sent: Tuesday, September 26, 2006 3:32:06 PM Subject: Lucene In Action Book vs Lucene 2.0 Hi, I have bought the Lucene In Action Book for more than

Lucene In Action Book vs Lucene 2.0

Hi, I have bought the Lucene In Action Book for more than a year now, and was using Lucene 1.x during that time. Now, I have a new project with Lucene and Lucene is now 2.0. Many APIs seems to have changed. I would like to ask the experts here, what are the important or substantial changes from

Re: How to combine multiple fields to a single field for indexing

Thanks. I think I grasp the concept now :) On 8/27/06, Erik Hatcher <[EMAIL PROTECTED]> wrote: On Aug 26, 2006, at 5:11 AM, KEGan wrote: > Erik, > > "Given the position increment gap between instances of same-named > fields that is now part of Lucene, I recomme

Re: How to combine multiple fields to a single field for indexing

that your analyzer won't eat up, so that > will > change the token position by 1. > > Gopi > > On 8/24/06, KEGan <[EMAIL PROTECTED]> wrote: >> >> Erik, >> >> What is generally the reason for indexing both individual fields, >> and the >

Re: How to combine multiple fields to a single field for indexing

I think I start to understand this :) .. Thanks guys. ~KEGan On 8/24/06, Gopikrishnan Subramani <[EMAIL PROTECTED]> wrote: Erik's has used a space as the field separator. May be you can use a different field separator that your analyzer won't eat up, so that will change the t

Re: How to combine multiple fields to a single field for indexing

Erik, What is generally the reason for indexing both individual fields, and the general-purpose "content" field ? Also, if we search in the general-purpose "content" field, wouldnt this problem occurs. Let say we have 2 fields and the following values: name : John Smith food : subway sandwich

Luke for Lucene 2.x ?

please let us know :) Thanks. ~KEGan