We are dependent on the java version supported by Hadoop distributions. Last I checked Cloudera supports Java7 so we cannot take out the support for that.
Thanks, Chandni On Wed, Dec 2, 2015 at 7:56 AM, Ted Dunning <[email protected]> wrote: > Just a question for discussion ... > > Is Java7 support really necessary? Why not just go with JDK8 so you don't > need Joda time at all. The java.time classes are very similar and where > they differ, they seem superior (which makes sense given they used the > experience of Joda time heavily). > > Java7 is now not receiving public updates since April, 2015 (java 7u79). Do > we really want to encourage users to use software that isn't even getting > security updates outside of special support contracts? > > > > On Wed, Dec 2, 2015 at 2:40 PM, Sandeep Deshmukh <[email protected]> > wrote: > > > Good idea Chandni. This is what I get from their page and makes perfect > > sense to use it going forward. > > --------------------- > > Joda-Time is the *de facto* standard date and time library for Java. From > > Java SE 8 onwards, users are asked to migrate to java.time (JSR-310). > > --------------------- > > > > Regards, > > Sandeep > > > > On Mon, Nov 30, 2015 at 1:50 PM, Chandni Singh <[email protected]> > > wrote: > > > > > Hi, > > > > > > We should consider replacing TimeBucket class with Period in Joda Time > > > library when creation of arbitrary time buckets are allowed, for eg. > 5H, > > > 3d, etc. > > > > > > Joda Time library is popular and widely used. It has Duration and > Period > > > classes that are very convenient. These classes have been added to JDK > 8. > > > > > > I will be using Joda library for ManagedState implementation. > > > > > > Thanks, > > > Chandni > > > > > >
