You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Alan Woodward (Jira)" <ji...@apache.org> on 2020/02/04 14:13:00 UTC

[jira] [Commented] (LUCENE-9204) Move span queries to the queries module

    [ https://issues.apache.org/jira/browse/LUCENE-9204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17029860#comment-17029860 ] 

Alan Woodward commented on LUCENE-9204:
---------------------------------------

Originally suggested by Mike as a comment in LUCENE-6871

This also allows some cleaning up of ConjunctionDISI, DisiWrapper and DisiPriorityQueue, in that they don't need parallel structures for Scorers and Spans.

The one piece of functionality that becomes unavailable is in QueryBuilder, which currently uses span queries to build query graphs - eg, if you have a multi-term synonym as part of your query, QB turns that into a span query with an OR in the middle of it.  Given LUCENE-7398 though, I think it's better to just fall back to creating a phrase query for each path through the graph, and combining those.  This is what QB does now if you pass through a non-zero slop anyway, and the scoring makes more sense (SpanOrQuery scoring includes stats for all of its sub-terms, even if they don't actually appear in any matches).

 

> Move span queries to the queries module
> ---------------------------------------
>
>                 Key: LUCENE-9204
>                 URL: https://issues.apache.org/jira/browse/LUCENE-9204
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Alan Woodward
>            Assignee: Alan Woodward
>            Priority: Major
>
> We have a slightly odd situation currently, with two parallel query structures for building complex positional queries: the long-standing span queries, in core; and interval queries, in the queries module.  Given that interval queries solve at least some of the problems we've had with Spans, I think we should be pushing users more towards these implementations.  It's counter-intuitive to do that when Spans are in core though.  I've opened this issue to discuss moving the spans package as a whole to the queries module.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org