You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apex.apache.org by Sandeep Deshmukh <sa...@datatorrent.com> on 2015/12/02 04:40:55 UTC
Re: Period class in Joda Time library as a replacement of TimeBucket
in appdata/schemas
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 <ch...@datatorrent.com>
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
>
RE: Period class in Joda Time library as a replacement of
TimeBucket in appdata/schemas
Posted by "Frew, Troy" <Tr...@capitalone.com>.
CDH 5.5 still packages java7 in the manager/parcel install.
Sent with Good (www.good.com)
-----Original Message-----
From: Chandni Singh [chandni@datatorrent.com<ma...@datatorrent.com>]
Sent: Wednesday, December 02, 2015 11:44 AM Eastern Standard Time
To: dev@apex.incubator.apache.org
Subject: Re: Period class in Joda Time library as a replacement of TimeBucket in appdata/schemas
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 <te...@gmail.com> 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 <sa...@datatorrent.com>
> 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 <ch...@datatorrent.com>
> > 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
> > >
> >
>
________________________________________________________
The information contained in this e-mail is confidential and/or proprietary to Capital One and/or its affiliates and may only be used solely in performance of work or services for Capital One. The information transmitted herewith is intended only for use by the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any review, retransmission, dissemination, distribution, copying or other use of, or taking of any action in reliance upon this information is strictly prohibited. If you have received this communication in error, please contact the sender and delete the material from your computer.
Re: Period class in Joda Time library as a replacement of TimeBucket
in appdata/schemas
Posted by Chandni Singh <ch...@datatorrent.com>.
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 <te...@gmail.com> 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 <sa...@datatorrent.com>
> 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 <ch...@datatorrent.com>
> > 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
> > >
> >
>
Re: Period class in Joda Time library as a replacement of TimeBucket
in appdata/schemas
Posted by Ted Dunning <te...@gmail.com>.
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 <sa...@datatorrent.com>
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 <ch...@datatorrent.com>
> 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
> >
>