Re: OOM when using Lucene 5.X's group facet collectors on unsharded index

2015-07-06 Thread Adam Rosenwald
Correction. The three facet fields used to initialize the TermGroupFacetCollectors are SortedDVs - not SortedNumericDVs. On 07/06/2015 04:56 PM, Adam Rosenwald wrote: Hello all, When using Lucene 5.X's group facet collectors (i.e. *AbstractGroupFacetCollector* and the provided concrete

OOM when using Lucene 5.X's group facet collectors on unsharded index

2015-07-06 Thread Adam Rosenwald
Hello all, When using Lucene 5.X's group facet collectors (i.e. *AbstractGroupFacetCollector* and the provided concrete implementation, *TermGroupFacetCollector*), I repeatedly encounter OOM errors after running a few search requests on an unsharded index consisting of a few million docum

Re: Upgrading Lucene 4 index to 5 doesn't update it - for just some indices

2015-07-06 Thread Trejkaz
> The problem are not the class names, the problem are the names as > written to Index. And in a Lucene 4 index there is written e.g., "Lucene47" > as Codec and Postingsformat. The lookup by name is done by this name. > IndexReader/Writer does Codec.forName("Lucene47"). For this to work, > every co

RE: Upgrading Lucene 4 index to 5 doesn't update it - for just some indices

2015-07-06 Thread Uwe Schindler
Hi, > On Mon, Jul 6, 2015 at 4:32 PM, Uwe Schindler wrote: > > Hi, > > > > It could be the reason for this is your classpath: > > > > If you load all Lucene Versions into the same classloader (but with > > different > package names - I assume you use Maven Shade plugin to do this), Lucene 3 > wi

Re: Upgrading Lucene 4 index to 5 doesn't update it - for just some indices

2015-07-06 Thread Trejkaz
On Mon, Jul 6, 2015 at 4:32 PM, Uwe Schindler wrote: > Hi, > > It could be the reason for this is your classpath: > > If you load all Lucene Versions into the same classloader (but with different > package names - I assume you use Maven Shade plugin to do this), Lucene 3 > will load perfectly, y