Re: Lucene Error List

Be sure to error trap the exception Boolean.TooManyClauses specifically and the core RuntimeException as the secondary trap. For the Boolean.TooManyClauses exception, I give the user a message like, "Too broad of a search. Try again". Searches like "f*" will produce this exception. Also, the wi

Looking for Similarity Subclass Examples

Hello list, I am working on boosting query performance by writing my own Similarity Class (Rewrite tf(), idf(), boost(), lengthNorm()). I've gone through the defaultSimilarity class. Does anyone know other examples of Similarity Class Implementation and point me to that direction? Thanks. Jack

Re: AW: AW: Determine the index of a hit after using MultiSearcher

We are not planning on anything servlet-specific - servlets are really nothing special. But we are planning on LIA 2.0. Not sure about the timing yet (but I can tell you we haven't started writing anything just yet). Otis --- Malcolm <[EMAIL PROTECTED]> wrote: > Are you going to write another

Re: Determine the index of a hit after using MultiSearcher

On Tuesday 29 November 2005 22:42, Paul Elschot wrote: > On Tuesday 29 November 2005 14:47, [EMAIL PROTECTED] wrote: > > Hello, > > > > I am searching over multiple indices using MultiSearcher. Thus I get hits > > from various indices. Is it possible to determine from which index a hit > > comes?

Re: Determine the index of a hit after using MultiSearcher

On Tuesday 29 November 2005 14:47, [EMAIL PROTECTED] wrote: > Hello, > > I am searching over multiple indices using MultiSearcher. Thus I get hits > from various indices. Is it possible to determine from which index a hit > comes? Yes: use the subIndex() and maybe subDoc() methods here: http://l

Re: AW: AW: Determine the index of a hit after using MultiSearcher

Are you going to write another addition with lots of Servlet code? If that's the case put me down for an advance copy.Lucene and servlets is a direction I may be going in the future. Thanks, Malcolm Clark - To unsubscribe, e

Re: AW: AW: Determine the index of a hit after using MultiSearcher

On 29 Nov 2005, at 10:05, Stefan Gusenbauer wrote: This is an other good reason for buying the book ultimately! Well, unfortunately, this particular trivia isn't covered in the book, but rather behind the scenes of the website about the book. I will mark this as something to add to the 2n

AW: AW: Determine the index of a hit after using MultiSearcher

This is an other good reason for buying the book ultimately! Thx stefan -Ursprüngliche Nachricht- Von: Erik Hatcher [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 29. November 2005 15:57 An: java-user@lucene.apache.org Betreff: Re: AW: Determine the index of a hit after using MultiSearche

Re: AW: Determine the index of a hit after using MultiSearcher

On 29 Nov 2005, at 08:51, Stefan Gusenbauer wrote: I've done this in the same way every document contains a field with the corresponding index. I fear there is no other way to do this. Fear not. There is a way. In fact, lucenebook.com uses this capability to determine whether a search h

RE: Determine the index of a hit after using MultiSearcher

There's a public method "int subSearcher(int n)" in MultiSearcher. If you pass it a document id (not the hit sequence number!), it returns the number of the searcher that contains that document id (in the array you passed to the constructor of MultiSearcher) Luc -Original Message- From

Re: Caching Results

Well, this depends, in case you have a small index just some million documents that it make no sense. But in case you have some hundred millions documents and may use distributed searching it makes a lot of sense. Just check ehcache.sf.net i found it very useful. HTH Stefan Am 29.11.2005 um 1

Caching Results

I have some queries that are run numerous times a day..is it better to cache results such that I would run a filter once and then cache it, and with the Term clause run the query? Is it better for me to instead look into optimizing my code and query? I am trying to get some thoughts on caching

AW: Determine the index of a hit after using MultiSearcher

I've done this in the same way every document contains a field with the corresponding index. I fear there is no other way to do this. -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 29. November 2005 14:48 An: java-user@lucene.apache.org Be

Determine the index of a hit after using MultiSearcher

Hello, I am searching over multiple indices using MultiSearcher. Thus I get hits from various indices. Is it possible to determine from which index a hit comes? The solution I found is to store the index in a document's field, but this causes some overhead. I would like to find another solution.

Re: Search Problem

Lucene is case sensitive. Make sure the case in your query matches the case in the index. You could also try selecting the keyword analyser in Luke. I've done both, but the results are as written. Dirk - To unsubscribe, e-m

Re: Search Problem

Lucene is case sensitive. Make sure the case in your query matches the case in the index. You could also try selecting the keyword analyser in Luke. Paul I. Dirk Hennig

Re: Search Problem

Hi Pierrick, It is very likely that the analyzer bound to your query parser filters "pdf" out, maybe because it has only 3 letters, Luke shows me "filetype:pdf" as parsed and rewritten query. I think than this can't be the problem or am I wrong on this? Greetings, Dirk

Re: Search Problem

Hi, Dirk Hennig wrote: Even the simple query "+filetype:pdf" returns no results. But "+filetype:html" works perfect. How can this be? Has anyone an idea? It is very likely that the analyzer bound to your query parser filters "pdf" out, maybe because it has only 3 letters, Cheers, -- Pier

Search Problem

Hallo, I have a simple index which includes only text (in a field "text") from 2 different type of files: html and pdf. I'm using a field "filetype" to store from which type the text came. This field holds a value "html" or "pdf". Now, if I browse the index with Luke, I can see all documents, t

Re: Lucene and DB interactions

I would start reading 'I love Lucene' article on The Server Side. Regards, Daniel Blanch - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]