Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of serera@gmail.com designates
 209.85.160.48 as permitted sender)
MIME-Version: 1.0
Date: Thu, 15 Nov 2012 12:39:08 +0200
Message-ID: 
 <CALfq-2RXO+LDAwqM9OHGWdTvzCCRW1aJQiFSe+Knav4hJ1EeQw@mail.gmail.com>
Subject: Question about CompressingCodec
From: Shai Erera <serera@gmail.com>
To: dev@lucene.apache.org
Content-Type: multipart/alternative; boundary=e89a8ff1ccd2c9fd8404ce864238

--e89a8ff1ccd2c9fd8404ce864238
Content-Type: text/plain; charset=ISO-8859-1

Hi

I looked at CompressingCodec and had a couple of questions until I realized
it's a test code only. I understand that creating a Codec class is not
favorable, because of back-compat issues (that may arise in the future), so
I'll ask that -- what if we made it a non-test class, which takes any Codec
to wrap (i.e. not default to Lucene41Codec)? I don't have any strong
feelings for or against it, so I'm ok if the general feeling is that we
should provide CompressingStoredFieldsFormat only.

While at that, should CompressingStoredFieldsFormat be named
CompressingStoredFieldsFormat41 or something like that, preparing it for
future changes? Or ... or we can add the version to the name only when it's
actually changed ...

Shai

--e89a8ff1ccd2c9fd8404ce864238
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi<br><br>I looked at CompressingCodec and had a coup=
le of questions until I realized it&#39;s a test code only. I understand th=
at creating a Codec class is not favorable, because of back-compat issues (=
that may arise in the future), so I&#39;ll ask that -- what if we made it a=
 non-test class, which takes any Codec to wrap (i.e. not default to Lucene4=
1Codec)? I don&#39;t have any strong feelings for or against it, so I&#39;m=
 ok if the general feeling is that we should provide CompressingStoredField=
sFormat only.<br>
<br>While at that, should CompressingStoredFieldsFormat be named Compressin=
gStoredFieldsFormat41 or something like that, preparing it for future chang=
es? Or ... or we can add the version to the name only when it&#39;s actuall=
y changed ...<br>
<br></div>Shai<br></div>

--e89a8ff1ccd2c9fd8404ce864238--