is that we have a Hadoop-2.6 (or whatever
> > > > version)
> > > > > branch, make all the upgrade related changes there (which should
> be a
> > > > list
> > > > > of JIRAs) and then merge it back to master when we
eted.
> > > >
> > > > Thomas
> > > >
> > > >
> > > >
> > > > On Tue, Jul 12, 2016 at 8:36 AM, Chinmay Kolhatkar <
> > > > chin...@datatorrent.com>
> > > > wrote:
> > > >
> > > &g
torrent.com>
> > > wrote:
> > >
> > > > I'm -0 on this idea.
> > > >
> > > > Here is the reason:
> > > > Unless we see a real case where users want to see everything on
> latest,
> > > > this branch might quic
-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 re
> really
> > > make it bleeding edge. Specially about malhar, its a long list. That
> > looks
> > > like quite significant work.
> > > Moreover, if this branch is going to be in "may or may not work" state;
> > I,
> > > as a user or
anch is going to be in "may or may not work" state;
> I,
> > as a user or developer, would bank on what certainly works.
> >
> > I also think that, if its going to be "no gaurantee" then its worth
> > spending time contributions towards master rathe
e significant work.
> Moreover, if this branch is going to be in "may or may not work" state; I,
> as a user or developer, would bank on what certainly works.
>
> I also think that, if its going to be "no gaurantee" then its worth
> spending time contributions t
k that, if its going to be "no gaurantee" then its worth
spending time contributions towards master rather than bleeding-edge branch.
If a question of "should we upgrade?" comes, the community is mature to
take that call then and work accordingly.
-Chinmay.
On Tue, Jul 12, 2016 at 11:4
and other such changes.
>
> As always, I'm open to other ideas, but that is what I had in mind when I
> made the suggestion.
>
> Ram
>
>
>
> On Mon, Jul 11, 2016 at 1:45 PM, Sanjay Pujare <san...@datatorrent.com>
> wrote:
>
> > As the name suggests the "
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 <da...@datatorre
gt; 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, upgrad
t;
> 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
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 the
13 matches
Mail list logo
