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 13:36:07 GMT


Uwe Schindler commented on LUCENE-1687:

bq. True, but you know how we are about adding methods to an interface! 
Yonik said it: Because nobody can change a static variable in an interface (its always final),
there is no posibility to change the cache impl, so nobody would ever implement FieldCache.
A short notice should be enough.

Should I fix this together with LUCENE-1701? If yes, I would assign myself to this issue and
add this to my own patch (which also fixes some issues by making the default parsers public).

I would then only deprecate  ExtendedFieldCache (as sub-interface of FieldCache, without new
methods) and merge the two package-private impls behind.

> Remove ExtendedFieldCache by rolling functionality into FieldCache
> ------------------------------------------------------------------
>                 Key: LUCENE-1687
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Grant Ingersoll
>            Assignee: Grant Ingersoll
>            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