lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] [Commented] (SOLR-2660) omitPositions improvements
Date Wed, 06 Mar 2013 14:52:13 GMT


Robert Muir commented on SOLR-2660:

There is no exception to fix. I think people discussing in that thread have a misunderstanding
of what this issue is about.
If you ask to omit positions, and then you ask for a phrase query, or configure a stupid query
parser that generates them automatically, then you deserve an exception.

> omitPositions improvements
> --------------------------
>                 Key: SOLR-2660
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>    Affects Versions: 3.3, 4.0-ALPHA
>            Reporter: Robert Muir
>            Priority: Minor
>         Attachments: SOLR-2660.patch
> followup to LUCENE-2048:
> Adds factory methods getPhraseQuery/getMultiPhraseQuery to QP, this way you can subclass
it and customize behavior, particularly
> * by default, Solr throws exception here if the fieldtype omits positions: rather than
3.x's silent failure of no results, and even for trunk its nicer to fail during query parsing
rather than waiting for lucene's failure during execution.
> * adds phraseAsBoolean, which allows you to downgrade these phrase/multiphrase queries
to boolean queries: this is a nice option in conjunction with our word n-gram filters (shingle/commongrams/etc)for
a fast "approximation", if your application can tolerate some false positives, e.g. "foo bar"
-> termQuery(foo_bar), "foo bar baz" -> BQ(foo_bar AND bar_baz)

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

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

View raw message