lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael McCandless <luc...@mikemccandless.com>
Subject Re: SortingMergePolicy in Lucene 6
Date Wed, 25 May 2016 19:07:33 GMT
Sorry, yes, dimensional points and SlowCompositeReaderWrapper are not
compatible.

This class (SlowCompositeReaderWrapper) is a terrible class that we have
been gradually (past 7 years) phasing out of Lucene.  It's a leaky
abstraction (http://www.joelonsoftware.com/articles/LeakyAbstractions.html)
that pretended your index has one segment when it doesn't, and it limited
our freedoms when developing new features.

Finally just today, for 7.0 anyways, we succeeded:
https://issues.apache.org/jira/browse/LUCENE-7283

That said, we have also fixed index time sorting to no longer use
SlowCompositeReaderWrapper:
https://issues.apache.org/jira/browse/LUCENE-6766

Right now this is a 7.0 (master) only change but I plan to backport for 6.2
once we get 6.1 released.  Maybe you could test Lucene's current master and
confirm points and index-time sorting work correctly for you?

Mike McCandless

http://blog.mikemccandless.com

On Wed, May 25, 2016 at 1:10 PM, Sheng <shengcer@gmail.com> wrote:

> It makes a call to SlowCompositeReaderWrapper in line 103, which checks if
> field hasPointValues in line 68. If yes, it throws an exception "cannot
> wrap points". Does this essentially mean SortingMergePolicy cannot be used
> for index that has point values. If yes, what is the rationale behind it ?
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message