lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Currens (Closed) (JIRA)" <>
Subject [jira] [Closed] (LUCENENET-479) QueryParser.SetEnablePositionIncrements(false) doesn't work
Date Fri, 23 Mar 2012 01:42:22 GMT


Christopher Currens closed LUCENENET-479.

    Resolution: Fixed

This was fixed along with re-porting the parser in LUCENENET-478.

Additionally, SetEnablePositionIncrements and GetEnablePositionIncrements now uses a bool
instead of a class, and is now a public property with a getter and setter (EnablePositionIncrements)
> QueryParser.SetEnablePositionIncrements(false) doesn't work
> -----------------------------------------------------------
>                 Key: LUCENENET-479
>                 URL:
>             Project: Lucene.Net
>          Issue Type: Bug
>          Components: Lucene.Net Core
>    Affects Versions: Lucene.Net 2.9.2, Lucene.Net 2.9.4, Lucene.Net 2.9.4g
>            Reporter: Christopher Currens
>             Fix For: Lucene.Net 3.0.3
> Trying to disable position increments via SetEnablePositionIncrements(false) has no effect,
at least on phrase queries.
> The parsed query returned from the QueryParser with this input, should by default return
a phrase query whose terms look like: "Query with Stopwords" should look silmilar to this
if converted to a string: "query ? stopwords", where ? is a null term query in the phrase
> With EnablePositionIncrements set to false, the resulting query should be similary to
"query stopwords".  However, calling SetEnablePositionIncrements(false) has no effect on the
resulting query.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message