[
https://issues.apache.org/jira/browse/LUCENE-9207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17031526#comment-17031526
]
Jim Ferenczi commented on LUCENE-9207:
--------------------------------------
+1, I agree that the current optimization can help in some cases but the crazy
expansion that can arises on phrase queries of shingles of different size
should be considered a bug. We already disable graph queries in Elasticsearch
if the analyzer contains a filter that is known to produce paths that don't
align (shingles of different size in the same field) so we could probably add
the same mechanism in Solr. I am also less worried by this issue now that we
eagerly check the number of path while building (and throw max boolean clause
if the number of paths is above the max boolean clause).
> Don't build SpanQuery in QueryBuilder
> -------------------------------------
>
> Key: LUCENE-9207
> URL: https://issues.apache.org/jira/browse/LUCENE-9207
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Alan Woodward
> Assignee: Alan Woodward
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Subtask of LUCENE-9204. QueryBuilder currently has special logic for graph
> phrase queries with no slop, constructing a spanquery that attempts to follow
> all paths using a combination of OR and NEAR queries. Given the known bugs
> in this type of query (LUCENE-7398) and that we would like to move span
> queries out of core in any case, we should remove this logic and just build a
> disjunction of phrase queries, one phrase per path.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
