[
https://issues.apache.org/jira/browse/LUCENE-8882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16873002#comment-16873002
]
Atri Sharma commented on LUCENE-8882:
-------------------------------------
I think this is useful even outside LUCENE-8881 – This allows upper queries to
collect metadata about the lower leaf level queries and make decisions
(motivated by the excellent work done recently to use the property of a sorted
index to perform binary searches on docIDs). So we could use a property such as
INDEX_SORTED, which is populated at some query and visible to the entire query
tree, and then a query looks at the property and decides to use a specific type
of query. This can even be ingested in the cost of the query, but in a
localised form so that not all heuristics are crammed in one specialized query
(IndexOrDocValues?)
Objections/Thoughts/Comments?
> Add State To QueryVisitor
> -------------------------
>
> Key: LUCENE-8882
> URL: https://issues.apache.org/jira/browse/LUCENE-8882
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Atri Sharma
> Priority: Major
>
> QueryVisitor has no state passed in either up or down recursion. This limits
> the width of decisions that can be taken by visitation of QueryVisitor. For
> eg, for LUCENE-8881, we need a way to specify is the visitor is a rewriter
> visitor.
>
> This Jira proposes adding a property bag model to QueryVisitor, which can
> then be referred to by the Query instance being visited by QueryVisitor.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
