Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
4.0-ALPHA
-
None
-
New, Patch Available
Description
Out of the discussion in LUCENE-2868, it could be useful to add a generic Query Visitor / Walker that could be used for more advanced rewriting, optimizations or anything that requires state to be stored as each Query is visited.
We could keep the interface very simple:
public interface QueryVisitor { Query visit(Query query); }
and then use a reflection based visitor like Earwin suggested, which would allow implementators to provide visit methods for just Querys that they are interested in.
Attachments
Attachments
Issue Links
- relates to
-
LUCENE-3056 Support Query Rewriting Caching
- Open
-
LUCENE-8184 Enable flexible Query.rewrite
- Open
-
LUCENE-5718 More flexible compound queries (containing mtq) support in postings highlighter
- Resolved
- links to