[
https://issues.apache.org/jira/browse/LUCENE-5114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13710334#comment-13710334
]
Robert Muir commented on LUCENE-5114:
-------------------------------------
{quote}
In all cases the API must break, or will only invite bugs.
What bugs? There wasn't any caching in the first place; it was effectively a
no-op.
{quote}
The bugs are when you make a method non-final, then its easy for the "wrong
method"
to be called.
Sophisticated compatibility can be added (using o.a.l.util.VirtualMethod), but
this
should be reserved for core apis where the change is necessary and we really
*need*
back compat.
For experimental apis, don't take the risk! just backwards break.
> remove boolean useCache param from TermsEnum.seekCeil/Exact
> -----------------------------------------------------------
>
> Key: LUCENE-5114
> URL: https://issues.apache.org/jira/browse/LUCENE-5114
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 5.0, 4.5
>
> Attachments: LUCENE-5114.patch
>
>
> Long ago terms dict had a cache, but it was problematic and we removed it,
> but the API still has a relic boolean useCache ... I think we should drop it
> from the API as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
