[
https://issues.apache.org/jira/browse/LUCENE-8531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662397#comment-16662397
]
Michael Gibney edited comment on LUCENE-8531 at 10/24/18 3:06 PM:
------------------------------------------------------------------
Thanks [~thetaphi], and I agree that it would be a separate issue (^"Would it
be worth opening a new issue to consider introducing the ability to
specifically request construction of {{SpanNearQuery}} and/or {{inOrder=true}}
behavior?"). I've created LUCENE-8543, so discussion can move there if anyone's
interested.
I also created LUCENE-8544, proposing the addition of support for
{{(Multi)PhraseQuery}} phrase semantics in {{SpanNearQuery}}. I think it should
be achievable, at least in the context of a proposed patch for
[LUCENE-7398|https://issues.apache.org/jira/browse/LUCENE-7398?focusedCommentId=16630529#comment-16630529].
was (Author: mgibney):
Thanks [~thetaphi], and I agree that it would be a separate issue (^"Would it
be worth opening a new issue to consider introducing the ability to
specifically request construction of {{SpanNearQuery}} and/or {{inOrder=true}}
behavior?"). I've created LUCENE-8543, so discussion can move there if anyone's
interested.
I also created LUCENE-8544, proposing the addition of support for
{{(Multi)PhraseQuery}} phrase semantics in {{SpanNearQuery}}. I think it should
be achievable, at least in the context of a proposed patch for LUCENE-7398.
> QueryBuilder hard-codes inOrder=true for generated sloppy span near queries
> ---------------------------------------------------------------------------
>
> Key: LUCENE-8531
> URL: https://issues.apache.org/jira/browse/LUCENE-8531
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/queryparser
> Reporter: Steve Rowe
> Assignee: Steve Rowe
> Priority: Major
> Fix For: 7.6, master (8.0)
>
> Attachments: LUCENE-8531.patch
>
>
> QueryBuilder.analyzeGraphPhrase() generates SpanNearQuery-s with passed-in
> phraseSlop, but hard-codes inOrder ctor param as true.
> Before multi-term synonym support and graph token streams introduced the
> possibility of generating SpanNearQuery-s, QueryBuilder generated
> (Multi)PhraseQuery-s, which always interpret slop as allowing reordering
> edits. Solr's eDismax query parser generates phrase queries when its
> pf/pf2/pf3 params are specified, and when multi-term synonyms are used with a
> graph-aware synonym filter, SpanNearQuery-s are generated that require
> clauses to be in order; unlike with (Multi)PhraseQuery-s, reordering edits
> are not allowed, so this is a kind of regression. See SOLR-12243 for edismax
> pf/pf2/pf3 context. (Note that the patch on SOLR-12243 also addresses
> another problem that blocks eDismax from generating queries *at all* under
> the above-described circumstances.)
> I propose adding a new analyzeGraphPhrase() method that allows configuration
> of inOrder, which would allow eDismax to specify inOrder=false. The existing
> analyzeGraphPhrase() method would remain with its hard-coded inOrder=true, so
> existing client behavior would remain unchanged.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
