[
https://issues.apache.org/jira/browse/LUCENE-7699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876101#comment-15876101
]
Matt Weber commented on LUCENE-7699:
------------------------------------
[~jim.ferenczi] That check was intended, but as you said, it is essentially
pointless. I will remove it. Yes, I think {{GraphQuery}} should go as well.
It was only needed when we needed to detect the graph to apply minimum should
match and phrase slop which is no longer the case. Should that be separate
issue?
> Apply graph articulation points optimization to phrase graph queries
> --------------------------------------------------------------------
>
> Key: LUCENE-7699
> URL: https://issues.apache.org/jira/browse/LUCENE-7699
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Matt Weber
> Attachments: LUCENE-7699.patch
>
>
> Follow-up to LUCENE-7638 that applies the same articulation point logic to
> graph phrases using span queries.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
