Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of ndimiduk@gmail.com designates
 209.85.128.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CANZa=GvU+xAzLr=KVR-uU0Qmzz=uzdvMq52Tts1QKqm-L3Lp8g@mail.gmail.com>
References: 
 <CANZa=Gv5wE-mGcHdCpU+vHyzBO1BidqMrTaxm9ze4qjVHmD2YQ@mail.gmail.com>
 <CAMUu0w-+CUh9hxwguLhKXb9hBtMDYR8CCPAXcN3B6LFLsOmw0Q@mail.gmail.com>
 <CADcMMgHzkJtALHTqNgzRaNB-xMu0fFB-qSXaACSWKyO-8G47gA@mail.gmail.com>
 <CANZa=GvwzFu_8RTeqh-6npiVm0dXyNna3Od3CEGVujg4b93ZSQ@mail.gmail.com>
 <CAFb6HiJU7iud7zBynVpSBU6oGpLTFUAN=Xg9HTDnnX8BYi-2QA@mail.gmail.com>
 <CANZa=GvU+xAzLr=KVR-uU0Qmzz=uzdvMq52Tts1QKqm-L3Lp8g@mail.gmail.com>
From: Nick Dimiduk <ndimiduk@gmail.com>
Date: Wed, 24 Jul 2013 11:27:00 -0700
Message-ID: 
 <CANZa=GvjYXLJnLEmAHdEJ28=+23fa3r5s6mCQCw=KxreeF9bbA@mail.gmail.com>
Subject: Re: Data types stage 1 is ready for reivew
To: dev@hbase.apache.org
Content-Type: multipart/alternative; boundary=047d7b2e75ec667c2e04e2460f63

--047d7b2e75ec667c2e04e2460f63
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi everyone,

As of yesterday, I've posted "final" patched on both
HBASE-8201<https://issues.apache.org/jira/browse/HBASE-8201>and
HBASE-8693 <https://issues.apache.org/jira/browse/HBASE-8693>. The former
specifies on-disk format and the latter is the user-facing API. If you've
already left me a review, thank you; please have another look at these
patches. If you have an opinion here and haven't voiced it, we're
approaching the "forever hold your peace" part of the ceremony.

Thanks,
Nick

On Wed, Jul 17, 2013 at 9:33 AM, Nick Dimiduk <ndimiduk@gmail.com> wrote:

> Thanks for having a look. If you don't mind terribly, I responded to your
> comments on JIRA [0].
>
> Thanks,
> Nick
>
> [0]: https://issues.apache.org/jira/browse/HBASE-8693#comment-13711250
>
>
> On Wed, Jul 17, 2013 at 1:42 AM, Matteo Bertozzi <theo.bertozzi@gmail.com=
>wrote:
>
>> I was looking at the HBASE-8693 patch, and looks good to me for the
>> primitive types.
>> but I can't see how do you plan to evolve stuff like the struct.
>> By "evolve" I mean add/remove fields, or just query it with a subset of
>> fields.
>> the fields don't have an id, and on read you must specify all of them in
>> the same order as you've used for write.
>> (but maybe is just an immutable/fixed list of fields, and I'm ok with ju=
st
>> adding that info to the comment on top of the class)
>>
>>
>> Matteo
>>
>>
>>
>> On Wed, Jul 17, 2013 at 12:39 AM, Nick Dimiduk <ndimiduk@gmail.com>
>> wrote:
>>
>> > New patch posted. What do you think about the new isSkippable() and th=
e
>> > associated limitation in Struct?
>> >
>> > I also posted some "dogfeed" per Enis's suggestion.
>> >
>> > -n
>> >
>> > On Fri, Jul 12, 2013 at 1:38 PM, Stack <stack@duboce.net> wrote:
>> >
>> > > On Fri, Jul 12, 2013 at 1:10 PM, Enis S=C3=B6ztutar <enis@apache.org=
>
>> wrote:
>> > >
>> > > > Did some chatting with Nick today.
>> > > >
>> > > > I think it is really important to get this right, and for that we
>> would
>> > > > definitely need more eyes towards it. The current patch set is in =
a
>> > good
>> > > > state to bolster the discussion.
>> > > >
>> > > >
>> > >
>> > > I'll do another pass (Kicking others to give it a looksee too).
>> > > St.Ack
>> > >
>> >
>>
>
>

--047d7b2e75ec667c2e04e2460f63--