lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] Resolved: (SOLR-1505) Phrase query used when the value is not in quotas
Date Tue, 13 Oct 2009 21:57:32 GMT


Hoss Man resolved SOLR-1505.

    Resolution: Invalid

There's no bug here ... this is the expected behavior of the standard QueryParser -- when
a "chunk" of input passed to an Analyzer produces multiple tokens with non-zero position offsets
a phrase query is produced ... this is what makes NGrams, WordDelimiterFilter, and a host
of other features work.

If differnet behavior is desired, then an alternate QueryParser should be used (alternately:
an Analyzer where all tokens produced have the same position could be used, since QueryParser
interprets those as alternate tokens and produces a BooleeanQuery ... assuming that's what
you want)


In the future: if you see behavior that you don't understand, please send am email to solr-user
describing your goal, what you've tried so far, and the results you've gotten before assuming
it's a bug and opening a Jira issue.

> Phrase query used when the value is not in quotas
> -------------------------------------------------
>                 Key: SOLR-1505
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: Analysis
>    Affects Versions: 1.4
>            Reporter: Alex Baranov
> Example:
> In query specified the next criteria:  _title:water,ground_ (note: the value is not in
quotas). For "title" field solr.PatternTokenizerFactory used with pattern=", *". After analysis
Solr applies the query as phrase query: title:"water ground" which requires the presents of
both words, etc..
> So, basically  _title:water,ground_ acts in the same way as _title:"water,ground"_. There
is no way how to avoid phrase query.
> When value is not in quotas then phrase query shouldn't be used.

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

View raw message