[
https://issues.apache.org/jira/browse/LUCENE-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770525#action_12770525
]
Mark Miller edited comment on LUCENE-2011 at 10/27/09 2:37 PM:
---------------------------------------------------------------
Its because of the loss of whats going on in PayloadTermQuery - we also lose
some custom info from PayloadNearQuery - on first blush it seems best just to
leave the exp in the scorer for Span queries - its still gone from Scorer so I
don't see it as much of a problem myself - havn't thought on it much yet though.
I guess we could pull all that custom info up to the weight through the
span/payload stuff - but then each has to duplicate a bunch of the info from
the SpanWeight - it seems nicer just to leave things as they are, let the
Scorer do it, and cast. What do you think?
was (Author: [email protected]):
Its because of the loss of whats going on in PayloadTermQuery - we also
lose some custom info from PayloadNearQuery - on first blush it seems best just
to leave the exp in the scorer for Span queries - its still gone from Scorer so
I don't see it as much of a problem myself - havn't thought on it much yet
though.
> Remove deprecated Scorer.explain(int) method
> --------------------------------------------
>
> Key: LUCENE-2011
> URL: https://issues.apache.org/jira/browse/LUCENE-2011
> Project: Lucene - Java
> Issue Type: Task
> Components: Search
> Reporter: Uwe Schindler
> Fix For: 3.0
>
> Attachments: LUCENE-2011.patch, LUCENE-2011.patch, LUCENE-2011.patch,
> LUCENE-2011.patch
>
>
> This is the only remaining deprecation in core, but is not so easy to handle,
> because lot's of code in core still uses the explain() method in Scorer. So
> e.g. in PhraseQuery, the explain method has to be moved from Scorer to the
> Weight.
--
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: [email protected]
For additional commands, e-mail: [email protected]
