As the name suggests the "bleeding-edge" branch ideally should use bleeding edge versions so I would like to see Java 8 used there (and Hadoop 3 when it does eventually come out) to make the maintenance effort worthwhile...
On Mon, Jul 11, 2016 at 12:05 PM, David Yan <[email protected]> wrote: > I'm -0 on Java 8, but I'm +1 on the rest, and I'm especially strong +1 for > upgrading the Hadoop dependency version. > > Here are my reasons: > > - Hadoop 3 will require Java 8, but Hadoop 2.7.2 still supports Java 7 and > there will probably be some time (I'm guessing more than one year) for > Hadoop 3 to become GA and for major distros to support Hadoop 3. The > maintenance effort for having two branches, one for Java 7 and one for Java > 8 is not worth it at this time. > > - Apex currently uses Hadoop 2.2 dependencies, marked "provided". And > Hadoop 2.4 has been released more than two years ago, and it added a lot of > features in the API that Apex can make use of. Most distros already bundle > Hadoop 2.6 or later. Although some old versions of Cloudera that include > hadoop version earlier than 2.4 still have not reached end-of-life yet, the > number of users using those old versions is probably very small. > > David > > > On Mon, Jul 11, 2016 at 8:59 AM, Munagala Ramanath <[email protected]> > wrote: > > > We've had a number of issues recently related to dependencies on old > > versions > > of various packages/libraries such as Hadoop itself, Google guava, > > HTTPClient, > > mbassador, etc. > > > > How about we create a "bleeding-edge" branch in both Core and Malhar > which > > will use the latest versions of these various dependencies, upgrade to > Java > > 8 so > > we can use the new Java features, etc. ? > > > > This will give us an opportunity to discover these sorts of problems > early > > and, > > when we are ready to pull the trigger for a major version, we have a > branch > > ready > > for merge with, hopefully, minimal additional effort. > > > > There will be no guarantees w.r.t. this branch so people using it use it > at > > their own > > risk. > > > > Ram > > >
