[Lucene.Net] possible infinite loop bug in portuguese snowball stemmer?

Are there any known issues with snowball stemmers (portuguese in particular) going into some infinite loop? I have a problem that happens on a recurring basis where IndexWriter locks up on AddDocument and never returns (it has taken up to 3 days before we realize it), requiring manual killing o

Re: [Lucene.Net] How to add document to more than one index (but only analyze once)?

or NRT & master index? > > DIGY > > On Fri, Sep 9, 2011 at 5:33 PM, Robert Stewart wrote: > >> Is it possible to add a document to more than one index at the same time, >> such that document fields are only analyzed one time? For instance, to add >> document

[Lucene.Net] How to add document to more than one index (but only analyze once)?

Is it possible to add a document to more than one index at the same time, such that document fields are only analyzed one time? For instance, to add document to both a master index, and a smaller near real-time index. I would like to avoid analyzing document fields more than once but I dont se

[Lucene.Net] alternatives to FSDirectory for multi-threaded search performance

What are the recommended best practices for using FSDirectory vs. RamDirectory, etc. for use in multi-threaded search? In a previous version of Lucene.Net (1.9) I used a modified FSDirectory implementation which used a pool of open FileStream objects for each segment file, and handed them out i

Re: [Lucene.Net] Score(collector) called for each subReader - but not what I need

> (https://cwiki.apache.org/confluence/display/LUCENENET/Simple+Faceted+Search > ) > > DIGY > > > > -----Original Message- > From: Robert Stewart [mailto:robert_stew...@epam.com] > Sent: Friday, June 10, 2011 7:14 PM > To: > Subject: [Lucene.Net] Score(collector) call

[Lucene.Net] Score(collector) called for each subReader - but not what I need

levated to a higher level. Thanks Bob On Jun 9, 2011, at 4:33 PM, Robert Stewart wrote: > I found the problem. The problem is that I have a custom "query optimizer", > and that replaces certain TermQuery's within a Boolean query with a custom > Query and this qu

Re: [Lucene.Net] index version compatibility (1.9 to 2.9.2)?

ene segments)? I am sure that is not clear and will try to provide more detail soon. Thanks Bob On Jun 9, 2011, at 1:48 PM, Digy wrote: > Sorry no idea. Maybe optimizing the index with 2.9.2 can help to detect the > problem. > DIGY > > -----Original Message- > From: Rob

Re: [Lucene.Net] index version compatibility (1.9 to 2.9.2)?

t; result in data loss. > > DIGY > > -Original Message- > From: Robert Stewart [mailto:robert_stew...@epam.com] > Sent: Thursday, June 09, 2011 7:06 PM > To: lucene-net-...@lucene.apache.org > Subject: [Lucene.Net] index version compatibility (1.9 to 2.9.2)? > > I

[Lucene.Net] index version compatibility (1.9 to 2.9.2)?

I have a Lucene index created with Lucene.Net 1.9. I have a multi-segment index (non-optimized). When I run Lucene.Net 2.9.2 on top of that index, I get IndexOutOfRange exceptions in my collectors. It is giving me document IDs that are larger than max

[Lucene.Net] index version compatibility (1.9 to 2.9.2)?

I have a Lucene index created with Lucene.Net 1.9. I have a multi-segment index (non-optimized). When I run Lucene.Net 2.9.2 on top of that index, I get IndexOutOfRange exceptions in my collectors. It is giving me document IDs that are larger than maxDoc. My index contains 377831 document