lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] Commented: (LUCENE-2002) Add oal.util.Version ctor to QueryParser
Date Thu, 22 Oct 2009 16:18:59 GMT


Michael McCandless commented on LUCENE-2002:

bq. Many analyzers can use a stopfilter and one of the stopfilters params is to enable or
disable this setting.

In fact, I think we may have to un-deprecate StopFilter.get/setEnablePositionIncrementsDefault
for this reason?  Many analyzers do embed StopFilter without exposing control over this setting,
and so the only way (up to & including 2.9) to change the setting is to set the static
default with StopFilter.  If we remove that then we've taken that control away.

Or, with this issue I could add Version to all contrib analyzers that embed StopFilter.  I
think I like that solution better (we shouldn't be using static defaults).  I'll go forward
w/ that shortly unless any objections come up... this'd also take care of analyzers that use
StandardTokenizer (ie, we'll control fixing the acronym bug with Version as well).

> Add oal.util.Version ctor to QueryParser
> ----------------------------------------
>                 Key: LUCENE-2002
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>    Affects Versions: 2.9, 3.0
>            Reporter: Uwe Schindler
>            Assignee: Michael McCandless
>             Fix For: 2.9.1
>         Attachments: LUCENE-2002-29.patch
> This is a followup of LUCENE-1987:
> If somebody uses StandardAnalyzer with Version.LUCENE_CURRENT and then uses QueryParser,
phrase queries will not work, because the StopFilter enables position Increments for stop
words, but QueryParser ignores them per default. The user has to explicitely enable them.
> This issue would add a ctor taking the Version constant and automatically enable this
setting. The same applies to the contrib queryparser. Eventually also StopAnalyzer should
add this version ctor.
> To be able to remove the default ctor for 3.0 (to remove a possible trap for users of
QueryParser), it must be deprecated and the new one also added to 2.9.1.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message