Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Thu, 19 May 2011 13:41:47 +0000 (UTC)
From: "Robert Muir (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: 
 <451807214.26579.1305812507375.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Created] (LUCENE-3124) review
 CodecProvider/CoreCodecProvider/SchemaCodecProvider hierarchy
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

review CodecProvider/CoreCodecProvider/SchemaCodecProvider hierarchy
--------------------------------------------------------------------

                 Key: LUCENE-3124
                 URL: https://issues.apache.org/jira/browse/LUCENE-3124
             Project: Lucene - Java
          Issue Type: Task
            Reporter: Robert Muir


As mentioned on SOLR-1942, I think we should revisit the CodecProvider hierarchy.

Its a little bit confusing how the class itself isn't really "abstract" but is really an overridable implementation.

One idea would be to make CodecProvider an interface, with Lucene using a simple hashmap-backed impl and Solr using the schema-backed impl. This would be in line with how SimilarityProvider was done.

It would also be good to review all the methods in CodecProvider and see if we can minimize the interface...


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org