RE: Hardware Question

I'm a little late to this thread. But is there any performance difference between the compound index format and the multifile index format when *searching*? The Lucene book mentions a performance difference when *indexing*, but not when searching. Monsur > -Original Message- > From:

Re: IO bandwidth throttling

I've wanted something similar, for the same purpose -- to keep lucene from consuming disk I/O resources when another process is running on the same machine. A general solution might be to define a simple interface such as interface IndexInputOutputListener { void willReadBytes(int numberOfByt

Re: IO bandwidth throttling

Hi, > Ok, let me rephrase the question. Assuming the RAMDirectory holds > approximately 500 MB of data which needs to be written to the > filesystem, I'm afraid that sending this much data in one shot might > choke the NFS. Is there a parameter with FSDirectory with which I can > instruct Lucene t

Re: IO bandwidth throttling

Ok, let me rephrase the question. Assuming the RAMDirectory holds approximately 500 MB of data which needs to be written to the filesystem, I'm afraid that sending this much data in one shot might choke the NFS. Is there a parameter with FSDirectory with which I can instruct Lucene to restrict the

Re: IO bandwidth throttling

While not exactly what you are describing, you can use one of the IndexWriter parameters (maxBufferedDocs) to control the size of the RAMDirectory that's used as a buffer during indexing. Otis --- Gopikrishnan Subramani <[EMAIL PROTECTED]> wrote: > Hello, > > Is there a way I can control the IO

IO bandwidth throttling

Hello, Is there a way I can control the IO bandwidth utilized by Lucene? Here is my scenario. RAMDirectory is used to build a in-memory index and finally the index size approaches a limit, the contents are flushed to a FSDirectory. The index size could be approximately 512 MB. I'm a bit concerne

Re: Question on Wildcard

On Tuesday 02 August 2005 21:15, Aigner, Thomas wrote: > Daniel, > Thanks for the response.  I sure hope there is an easy way around this.. Depends on what "easy" means to you :-) I think you'd have to write your own query parser that extends QueryParser and overwrite getWildcardQuery() etc. On

RE: Question on Wildcard

Daniel, Thanks for the response. I sure hope there is an easy way around this.. 1) How can you get the wildcard (* at beginning or the end) to use a specialized filter? (i.e. Punctuation filter, or synonym filter, Or stemmer?) Thanks all, Tom -Original Message- From: Daniel Naber [mail

Re: Question on Wildcard

On Monday 01 August 2005 22:22, Aigner, Thomas wrote: > The filter does not seem to be called when I search for 56-TXT* even > though I use my extended analyzer which has the filter in it so the > items are not found due to the token being 56TXT due to the filter. The specified analyzer if not us

Re: how to free memory after index ist build.

: 2) I don't see the code to close your statement, connection, and : ResultSet. Those typically go to a finally block. I'm 85% sure that's the memory leak right there... in absence of a good memory profiler, have you tried commenting out all of the Lucene related code, to make sure that your bas

Re: how to free memory after index ist build.

Hi Jan, I don't know where your memory goes - it could be any number of things. For instance, somebody mentioned recently that some MySQL JDBC drivers have known memory leaks. To figure out where the memory leaks is, and what's consuming your RAM, run your application under a profiler (OptimizeI

Re: NEXT VERSION

No firm plan. But if you see new features that you want to use, I encourage you to use the version from SVN. It is quite stable - I'm using it in production on Simpy.com for example. Otis --- Karthik N S <[EMAIL PROTECTED]> wrote: > > > Hi Luceners > > Apologies.. > > Just eage

multiple fields in position increments

Is it possible to have multiple fields for the same token position? For example: Position Field Token ---- 0authorRajesh 0personRajesh 1contents is 2contents

how to free memory after index ist build.

I am using the Lucene 1.4.3 API. After building the index over 15 documents (~250 MB data), Lucene does not free the memory that is used during indexing. The searcher runs as a servlet under Tomcat. Every time the index is build new, the indexing process takes free memory, so after ten runs the

NEXT VERSION

  Hi Luceners Apologies.. Just eager to ask " WHEN IS THE NEXT VERSION OF LUCENE BE OUT " . [ I am awaiting to use the new features for  my exisiting ones ] ...;)   WITH WARM REGARDS HAVE A NICE DAY [ N.S.KARTHIK]