On Tue, Mar 11, 2014 at 12:10 PM, Nick Dimiduk <[email protected]> wrote:
> On Tue, Mar 11, 2014 at 11:40 AM, James Taylor <[email protected] > >wrote: > > > Hey Nick, > > Which changes to data type serialization? Yes, too late for 3.0/4.0. > > > > I was referring to PHOENIX-123. > Ah, yes: ARRAY is a new, not yet released type for Phoenix, so we have a bit of flexibility to change it until its release in 3.0/4.0. We should talk about how this can be supported in your new type system. > > I think for 5.0, we should pursue using your new type system (and Hive > too, > > I hope). > > > > Makes sense. Anything else Phoenix is requesting from HBase 1.0? > I've been tagging random HBase JIRAs as I see them when I think that they would help Phoenix: https://issues.apache.org/jira/browse/HBASE-9301?filter=12325995 I'm sure I've missed many, and I need to review this list. Will do so after our 3.0/4.0 release. Thanks! James > > On Tue, Mar 11, 2014 at 6:24 AM, Nick Dimiduk <[email protected]> wrote: > > > > > Heya, > > > > > > While watching these changes to data type serialization, it got me > > thinking > > > about what changes will be needed to the HBase implementations in order > > for > > > Phoenix to adopt them (I guess for a 5.0 release, it's too late for > 4.0, > > > right?) More generally, are there other backward incompatible features > > for > > > Phoenix that we should be thinking of in mind of 1.0? > > > > > > Thanks, > > > Nick > > > > > >
