[ https://issues.apache.org/jira/browse/LUCENE-1771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12739547#action_12739547 ]
Michael McCandless commented on LUCENE-1771: -------------------------------------------- bq. And break back compat?! Yeah, that seems reasonable to me. Anyone else? Right. Though, we'd fix all core/contrib Query classes to cutover to the new API. It'd only be external (custom) Query impls that'd hit this. I think a hard break is better than a subtle and rather shocking "my explain method just consumed XXX MB" failure. > Using explain may double ram reqs for fieldcaches when using > ValueSourceQuery/CustomScoreQuery or for ConstantScoreQuerys that use a > caching Filter. > ---------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: LUCENE-1771 > URL: https://issues.apache.org/jira/browse/LUCENE-1771 > Project: Lucene - Java > Issue Type: Bug > Components: Search > Reporter: Mark Miller > Assignee: Mark Miller > Fix For: 2.9 > > Attachments: LUCENE-1771.patch, LUCENE-1771.patch, LUCENE-1771.patch, > LUCENE-1771.patch > > -- 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