[
https://issues.apache.org/jira/browse/LUCENE-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13023561#comment-13023561
]
Simon Willnauer commented on LUCENE-3041:
-----------------------------------------
bq. I'm happy to settle with QueryProcessor#process
+1 - Chris are you cranking out a patch for this?
I think if we have a QueryProcessor we should somehow make it possible to
optionally hook it into IndexSearcher to essentially replace the direct call to
Query#rewrite
Eventually it should be the QueryProcessor's responsibility to rewrite the
query and pass the actual 'primitive' query to the searcher once done. I think
its good to keep that interface super lean and let more fancy impl. follow up
on it. Stuff like automatic dispatch for certain query types might need some
cglib magic or at least req. java 6 to perform so they might need to go to
contrib/misc.
> Support Query Visting / Walking
> -------------------------------
>
> Key: LUCENE-3041
> URL: https://issues.apache.org/jira/browse/LUCENE-3041
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Search
> Reporter: Chris Male
> Priority: Minor
>
> 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:
> {code}
> public interface QueryVisitor {
> Query visit(Query query);
> }
> {code}
> 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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
