[
https://issues.apache.org/jira/browse/LUCENE-10223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17440421#comment-17440421
]
Dawid Weiss commented on LUCENE-10223:
--------------------------------------
bq. and perhaps we should change it so that you get offsets of the inner match
as standard, and then the outer match is returned as part of the sub matches.
I think the offsets should be returned consistently with positions - it really
aligns well with the logic of what filter expressions are and how they behave
at runtime (for example in highlighting).
I cleaned up a lot of old cruft in the documentation. That module (flex parser)
is still a bit messy but like I said - I found the combination of different
things it offers incredibly useful in practice (multifield expansion, parse
tree node processors).
I'd appreciate some eyes on the patch as it's quite large. If there are no
objections, I'll commit it.
> Add interval function support to standard query parser
> ------------------------------------------------------
>
> Key: LUCENE-10223
> URL: https://issues.apache.org/jira/browse/LUCENE-10223
> Project: Lucene - Core
> Issue Type: New Feature
> Affects Versions: 9.1
> Reporter: Dawid Weiss
> Assignee: Dawid Weiss
> Priority: Minor
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> This issue adds syntactic support for expressing interval sub-clauses within
> queries that StandardQueryParser can parse.
> * (/) add documentation on what the syntax is to the issue and to the code.
> * (/) update migration guide (may not be compatible)
> * (/) mention min-should-match operator support for boolean queries.
> * (/) changes entry
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
