Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Message-ID: <583856549.1245507487477.JavaMail.jira@brutus>
Date: Sat, 20 Jun 2009 07:18:07 -0700 (PDT)
From: "Uwe Schindler (JIRA)" <jira@apache.org>
To: java-dev@lucene.apache.org
Subject: [jira] Commented: (LUCENE-1687) Remove ExtendedFieldCache by
 rolling functionality into FieldCache
In-Reply-To: <1260149154.1244808847681.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/LUCENE-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12722198#action_12722198 ] 

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: https://issues.apache.org/jira/browse/LUCENE-1687
>             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: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org