[
https://issues.apache.org/jira/browse/LUCENE-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12743323#action_12743323
]
Michael McCandless commented on LUCENE-1808:
--------------------------------------------
I don't remember why we had decided (when adding QueryWeight) to open it up,
but, I think opening it up makes sense for advanced use cases?
> make Query.createWeight public (or add back Query.createQueryWeight())
> ----------------------------------------------------------------------
>
> Key: LUCENE-1808
> URL: https://issues.apache.org/jira/browse/LUCENE-1808
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Query/Scoring
> Affects Versions: 2.9
> Reporter: Tim Smith
>
> Now that the QueryWeight class has been removed, the public QueryWeight
> createQueryWeight() method on Query was also removed
> i have cases where i want to create a weight for a sub query (outside of the
> org.apache.lucene.search package) and i don't want the weight normalized
> (think BooleanQuery outside of the o.a.l.search package)
> in order to do this, i have to create a static Utils class inside
> o.a.l.search, pass in the Query and searcher, and have the static method call
> the protected createWeight method
> this should not be necessary
> This could be fixed in one of 2 ways:
> 1. make createWeight() public on Query (breaks back compat)
> 2. add the following method:
> {code}
> public Weight createQueryWeight(Searcher searcher) throws IOException {
> return createWeight(searcher);
> }
> {code}
> createWeight(Searcher) should then be deprectated in favor of the publicly
> accessible method
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
