I thought Bigtop was the openSUSE of Big Data, moving foward without the of bleeding edge ;-)
All joking aside, I am with Cos on this. Just the existence of Bigtop has pushed the larger ecosystem to think being their own little gardens and that includes dropping deprecated components. I can remember not so long ago we had to drag in Java 1.5 to build docs for some stuff. I am confortable with our cruising speed. Thanks, Peter On Thu, 26 Jun 2014 17:15:38 -0700 Konstantin Boudnik <c...@apache.org> wrote: > On Thu, Jun 26, 2014 at 06:59PM, jay vyas wrote: > > Im not casting a vote :BUT thinking out loud: > > > > If bigtop is really the "fedora" of bigdata distros, then moving to > > Java 7 is the natural thing to do. > > I beg to differ: Bigtop is a Debian of bigdata ;) Agree with the rest > though. However, the question is about timing. I'd say: we can try to > give it a full build attempt using nothing but JDK7 and see how the > things are going. If something breaks - we can do 0.8.1. which will > only be focused on JDK7 upgrade. Thought? > > > Fedora integrates the trailblazing linux technology - without fear > > of consequences.... and I see BigTop as doing the exact same thing > > in the hadoop community. > > > > For me -- BigTop is a platform to innovate and do cool new stuff on > > -- so I say keep it that way and keep fearlessly moving forward :) > > > > > > On Thu, Jun 26, 2014 at 6:34 PM, Roman Shaposhnik > > <ro...@shaposhnik.org> wrote: > > > > > Hi! > > > > > > based on Andrew P. suggestion I bumped the > > > version of JDK6 to the latest update (45) and > > > it seems to have cured the HBase problem. > > > > > > As a side note: for a deprecated, unsupported > > > platform such as JDK6 there's no reason to use > > > anything but the latest version anyway. > > > > > > But even with that, we still do have quite a few > > > failures in various components (Hive, Pig, etc.). > > > > > > How do we attack it? Thoughts? > > > > > > Thanks, > > > Roman. > > > > > > > > > > > -- > > jay vyas
