AW: Leftover write.lock file

ng documents)." (see https://lucene.apache.org/core/6_0_1/core/org/apache/lucene/codecs/lucene60/package-summary.html ) which, judging from the code and the above post, is wrong, and perhaps could be corrected...? (Thanks in advance.) Best regards, Oliver Dipl.-Phys. Oliver Kaleske PTV GROUP

Re: Migration from 4-7-0 to 6-0-0

Hi, > For example I was not able to find: > 1) when the method FieldType.setIndexed(true) was dropped and how to > change coding 5.0, see https://issues.apache.org/jira/browse/LUCENE-6013 > 2) Same for the method Query.extractTerms 5.2, see https://issues.apache.org/jira/browse/LUCENE-6425 hth,

Re: Some segments in compound format, others not

] Gesendet: Mittwoch, 24. August 2016 11:09 An: Lucene Users <java-user@lucene.apache.org>; Oliver Kaleske <oliver.kale...@ptvgroup.com> Betreff: Re: Some segments in compound format, others not Hi Oliver, The default behavior of Lucene (well, TieredMergePolicy, the default m

Re: null Query from MultiFieldQueryParser.getFieldQuery

: Steve Rowe [mailto:sar...@gmail.com] Gesendet: Freitag, 30. September 2016 21:48 An: java-user@lucene.apache.org Cc: Oliver Kaleske <oliver.kale...@ptvgroup.com> Betreff: Re: null Query from MultiFieldQueryParser.getFieldQuery Hi Oliver, Thanks for reporting and for the analysis, this is

AW: How to build a Lucene BooleanQuery?

Try BooleanQuery.Builder builder = new BooleanQuery.Builder(); builder.add(subQuery1, occur1); builder.add(subQuery2, occur2); // ... BooleanQuery query = builder.build(); -Ursprüngliche Nachricht- Von: szzoli [mailto:reg9sz...@freemail.hu]

null Query from MultiFieldQueryParser.getFieldQuery

Hi, in updating Lucene from 6.1.0 to 6.2.0 I came across the following: We have a subclass of MultiFieldQueryParser (MFQP) for creating a custom type of Query, which calls getFieldQuery() on its base class (MFQP). For each of its search fields, this method has a Query created by calling

Some segments in compound format, others not

Hi, I noticed on some of my Lucene indexes that they consist of both segments in compound format and segments in non-compound format. There appears to be a pattern such that smaller segments (in terms of disk storage) are in compound format, and larger segments are non-compound. However, in one

RE: Migrate BooleanQuery Lucene 4.9.0 to Lucene 6.0.3

Hi, try BooleanQuery inner = new BooleanQuery.Builder().add(ownerQueryX, Occur.SHOULD).add(groupQueryY, Occur.SHOULD).build(); BooleanQuery constrainedQuery = new BooleanQuery.Builder().add(inner, Occur.MUST).add(query, Occur.MUST).build(); You can also split this into several