I want to see initial data type APIs ship out with 0.95.2. A patch for
ordered byte serialization is up (HBASE-8201) and is nearing steady-state.
However, sershe is the only person who's left feedback. I just posted an
early patch for the data type API itself (HBASE-8693). It should get some
eyes from all manor of interested parties, but I'll settle for folk from
Phoenix for now.
Should these tasks be escalated to criticals in order to grab attention?
Additional comments inline.
On Mon, Jun 24, 2013 at 9:53 AM, Stack <[EMAIL PROTECTED]> wrote:
> Lets do one last 'Development Release', a 0.95.2, and then a 0.96 release
> in August?
+ There are no blockers , just a few criticals, a few of which we should
> at least fix: failed hadoop2 unit tests
(The migration polishing should probably be a blocker)
Namespaces is the long pole and progress seems slow. Do we hold up the
> release for them? How can we hurry this effort along? Swat team descends
> on Y!?
It would be a shame to not get a decision on this in for 0.96.
+ Is anyone testing? Integration tests fail on ec2 build from time to time
> . Our Elliott dug in on one of the failures a few days back and found
> legit issue w/ no retry on admin tasks (I heart hbase-it tests). Our unit
> test story is better  but there are still the odd failures.
With the creation of the new list, noticing these issues is going to push
further back-burner. Nannying this stuff should retain focus. I'll
volunteer to track on these issues as I see them.
Notice though that some of the more recent failures are caused by lack of
disk space on the Jenkins build host.
+ The build is still not baked; publishing a different hbase for hadoop1
> and hadoop2 is still not done (This is my charge).
> Your 0.96 RM,
> 2. http://126.96.36.199/
> 3. https://builds.apache.org/view/H-L/view/HBase/job/hbase-0.95/
> On Tue, Apr 2, 2013 at 5:59 PM, Enis Söztutar <[EMAIL PROTECTED]>
> > Hi devs,
> > We(HWX) had some discussions with Stack this morning about the eventual
> > 0.96 release, and 0.95 stuff. Having 0.96 out sooner rather than later is
> > becoming crucial as time passes. We've talked about some of the
> > work items, and what areas to focus on.
> > Some of the notes are:
> > - HBASE-8015. Support for Namespaces (Francis owns it, and the patch
> > mostly done. We should get this in since this is the singularity)
> > - HBASE-7999 Add 'system' tables (this may turn into just adding a
> > namespace, and be done with it. Depends on HBASE-8015. )
> > - HBASE-8093. Change the META name (can be done together as a part of
> > HBASE-8015, HBASE-7999)
> > - HBASE-3787 Increment is non-idempotent but client retries RPC. Nonce
> > issue (idempotent) -> critical, Enis or Sergey will work on this.
> > - Tarball, maven -> Enis, Giri, Nick, Stack
> > - Jeffrey's log replay patch (It allows 2sec recovery for accepting
> > for regions. We can get this in disabled by default, and keep both
> > distributed log splitting, and log replay. In 96, we can make it rock
> > afterwards)
> > - Region locality fixes hbase-7932/7942 (Devaraj says that he was able
> > convince the hdfs guys to accept the patch.)
> > - IPC review (DD, Stack)
> > - Cell stuff review
> > - Cell support in Filters etc. -> These are important but no blockers,
> > maybe we can defer them to 1.0.
> > - HBASE-7897 Add support for tags to Cell Interface
> > - MTTR -> non blocker. The more we have the better
> > - Formal hadoop2 support -> DD, Ted, Nick, hadoop-2.0.4-alpha issue.
> > - prefix-tree module, storage module, mapred? -> Enis push for decision
> > here.
> > - HBASE-7704. migration tool that checks presence of HFile V1 files.
> > (Stack)