in CentOS
// rather than with the difference in the OS itself.
Term[] fieldTerms = new Term[ 1 ];
fieldTerms[0] = new Term( theFieldName, "" );
indexWriter.deleteDocuments( fieldTerms );
// End of code that did NOT always work for me.
Frank Geary
--
View this message in context:
http://lucene.
s never to
reopen an IndexReader from one RAMDir index to use for a different RAMDir
index. It sometimes works, but will fail some of the time.
Frank Geary
Frank Geary wrote:
>
> For the record - I haven't proven this yet - but here's my current theory
> of what is causing
looks like each IW writes to a private log file -- could you zip up
> all such files and attach as a zip file (CC me directly because the
> list strips attachments)? It can give me a bigger picture than just
> these fragments...
>
> Mike
>
> On Fri, Jan 22, 2010 at 12:02 PM, F
IW 49 [pool-2-thread-1]: LMP: level -1.0 to
4.1824718: 1 segments
[2009-12-27 23:07:17,201Z]: IW 49 [pool-2-thread-1]: alwaysMerge=true
[2009-12-27 23:07:17,201Z]: IW 49 [pool-2-thread-1]: CMS: now merge
[2009-12-27 23:07:17,201Z]: IW 49 [pool-2-thread-1]: CMS: index: _0:C1
[2009-12-27 23:0
t; as of 2.9).
>
> You shouldn't have to remove files yourself -- just open a new IW with
> create=true?
>
> Mike
>
> On Tue, Jan 12, 2010 at 11:02 AM, Frank Geary
> wrote:
>>
>> Thanks for the reply Mike. Your questions were good ones because I
>>
n your index? Also, try running with asserts
> enabled... it may catch whatever is happening, sooner.
>
> Do you hold open a single IW on the RAMDir, and re-use it? Or open
> and then close? What about the disk dir?
>
> Mike
>
> On Mon, Jan 11, 2010 at 1:42 PM, Frank Gea
Hi,
I'm using Lucene 2.4.1 and am seeing occasional index corruption. It shows
up when I call MultiSearcher.search(). MultiSearcher.search() throws the
following exception:
ArrayIndexOutOfBoundsException. The error is: Array index out of range: ###
where ### is a number representing an index
