Re: Rails and lucene

ucene via JRuby. I cannot recommend Ferret. -- Kyle Maxwell Software Engineer CastTV, Inc http://www.casttv.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Performance guarantees and index format

What do people think about modifying Lucene, such that iteration is performed in reverse? -- Kyle Maxwell Software Engineer CastTV, Inc http://www.casttv.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e

Re: Luke for Lucene 2.3?

i changes, such that running luke like this was not possible. -- Kyle Maxwell Software Engineer CastTV, Inc http://www.casttv.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Luke for Lucene 2.3?

I don't have time to properly create a project, etc, but I release my additions to the public domain, and disclaim all warranty. -- Kyle Maxwell Software Engineer CastTV, Inc http://www.casttv.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Lucene to index OCR text

m query utilizing the TermPositions iterator)? -- Kyle Maxwell Software Engineer CastTV, Inc http://www.casttv.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Field rank?

ssible if the user entered more complex > queries... One of the MultiFieldQueryParser's constructors has a field boost argument. -- Kyle Maxwell Software Engineer CastTV, Inc http://www.casttv.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Generalized proximity query performance

> > Hmmm.. can you give some more concrete examples of what you mean by this? > both in terms of the use case you are trying to satisfy, and in terms of > how your current code works ... you don't have to post code or give away > trade secrets, just describe it as a black box (ie: what is the input

Generalized proximity query performance

Hi again,As the subject would suggest I'm trying to implement a layer of proximity weighting over lucene. This has greatly increased search relevance, but at the same time has knocked down performance by a substantial amount (see footer). I am using a hand rolled query of the following form (impl

Re: Subset match query?

I understand how that recommendation could potentially cover fields with undesired terms mixed in with the desired terms. I fail to see that it covers the case where the undesired term(s) are last, i.e. "desired desired undesired." Could you please elaborate? Thanks! -Kyle On 10/3/07, Chris H

Subset match query?

I'm indexing a dataset with lots of short fields. I have determined that it would be useful to highly boost matches where every term in this field is represented in the query. i.e.: Query: lucene field matches Field: lucene field but not Field: lucene has a field ... Field: lucene field foo... I'