lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <>
Subject [jira] Commented: (LUCENE-1687) Remove ExtendedFieldCache by rolling functionality into FieldCache
Date Sat, 20 Jun 2009 14:18:07 GMT


Uwe Schindler commented on LUCENE-1687:

It breaks backwards compatibility in the case that somebody *implements* FieldCache/ExtendedFieldCache.
As Yonik pointed out, this is unlikely the case, as there is no possibility to plug this implementation
into Lucene, because you *cannot* change the FieldCache.DEFAULT interface variable (static
final). Because of this nobody would ever want to implement this interface, and if he does,
it would be nonsense and can break without problems.

BeSo, removing/changing this interfaces would *not* be a BW break, as long as we only think
of implementing FieldCache/ExtendedFieldCache

But we would really break backwards compatibility for all who *refer* to this interface! And
because of this, the dummy stub keeps there, that classes still referencing parsers and ExtendedFieldCache.EXT_DEFAULT
can still work.

> Remove ExtendedFieldCache by rolling functionality into FieldCache
> ------------------------------------------------------------------
>                 Key: LUCENE-1687
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Grant Ingersoll
>            Assignee: Uwe Schindler
>            Priority: Minor
>             Fix For: 2.9
> It is silly that we have ExtendedFieldCache.  It is a workaround to our supposed back
compatibility problem.  This patch will merge the ExtendedFieldCache interface into FieldCache,
thereby breaking back compatibility, but creating a much simpler API for FieldCache.

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:
For additional commands, e-mail:

View raw message