+ a clearly defined compatibility strategy between patch, minor, and major versions + known coprocessor interfaces. For example right now a coprocessor can use everything on HRegion. We need to distill what's useful into an interface. + (wishes for ponies and unicorns, probably not going to happen) better ops supports, such as sample puppet/chef/etc scripts
________________________________ From: Stack <st...@duboce.net> To: HBase Dev List <dev@hbase.apache.org> Sent: Monday, February 10, 2014 4:29 PM Subject: Re: DISCUSSION: 1.0.0 Keep them coming and I'll file issues against 1.0 version. Thanks lads, St.Ack On Mon, Feb 10, 2014 at 11:38 AM, Enis Söztutar <enis....@gmail.com> wrote: > + fix interface audience annotations (HBASE-10462). > + Continue on limiting some broad reaching interfaces (HCM, HCI, HTable) > See recent HBASE-10479 discussions) > + Promote HTableInterface vs HTable, getting connections from HCM and > getting tables there. > > > > On Mon, Feb 10, 2014 at 11:20 AM, Stack <st...@duboce.net> wrote: > > > On Mon, Feb 10, 2014 at 11:15 AM, Steve Loughran <ste...@hortonworks.com > > >wrote: > > > > > On 10 February 2014 09:24, Stack <st...@duboce.net> wrote: > > > > > > > Suggestions for 1.0.0 if if it is to come out in next month or so: > > > > > > > > + Update included libs (e.g. move to log4j2) > > > > > > > > > > love to see how that goes on -it looks good but I've not seen it in > > > production yet. I do note it has a NoSQL outputter, so there are good > > > opportunities for recursion > > > > > > > > Smile. > > >
