Skip to main content.
home | support | download

Back to List Archive

Re: coalesce_buffer_max_size

From: <jmruiz(at)not-real.boe.es>
Date: Tue Jul 30 2002 - 18:00:59 GMT
Hi,

On 30 Jul 2002, at 8:29, Bill Moseley wrote:

> 
> >Processing
> >http://www.rrze.uni-erlangen.de/institut/software/produkt/spss/allbus
> >/allbu
> s96.por...
> >err: Buffer too short in coalesce_word_locations. Increase
> >COALESCE_BUFFER_MAX_SIZE in config.h and rebuild.
> 
> I think you see that when you are indexing a file that has too many
> words (Jose, is that right?) which you would find when trying to index
> a large binary file.
> 

Yep, that's right.

> There was a case where someone reported that swish was not indexing
> the last part of a document.  It turned out that they had an embedded
> null char in the doc so swish determined that was the end of the
> document.  Now swish reports that warning and replaces the null with a
> space char.  That allows swish to continue indexing the document.  But
> in most cases the warning means you are trying to index a binary file.
> 
> Jose, could COALESCE_BUFFER_MAX_SIZE by dynamically adjusted?
> 

I made this array static for some reason that I cannot remember at
this moment. Let me look at it.

cu
Jose
Received on Tue Jul 30 18:04:35 2002