[
https://issues.apache.org/jira/browse/LUCENE-7699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15875734#comment-15875734
]
Michael McCandless commented on LUCENE-7699:
--------------------------------------------
+1, thanks [~mattweber]; this also fixes an adversarial combinatoric explosion
case.
bq. On a different note I also wonder if we should keep the specialized
GraphQuery. IMO it's not useful anymore especially if we use span queries for
quoted query.
+1 to phase out {{GraphQuery}}, I think: really, the "graph-ness" of the
situation should only be a transient thing, that happened during query parsing,
and was quickly translated into the equivalent query structure?
> 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
