You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by Reza Farivar <rf...@yahoo-inc.com.INVALID> on 2016/01/11 23:40:17 UTC
Java 8 for Storm 2.x?
I have started work on translating the util.clj to java (STORM-1226). I see some instances when translating the functional behavior of clojure to Java requires code that is already part of java 8.
For instance, there are many cases where a predicate function is passed around (e.g. in find-first). I can go ahead and implement a Predicate interface and use that, but Java 8 has already exactly that functionality implemented.
Would it make sense to move to Java 8 for the post-clojure branch 2.x?
--Reza
Re: Java 8 for Storm 2.x?
Posted by Reza Farivar <rf...@yahoo-inc.com.INVALID>.
Thanks for all your comments, I'll do that and make sure it remains compatible with Java 7.
--Reza
On Monday, January 11, 2016 6:14 PM, Jungtaek Lim <ka...@gmail.com> wrote:
+1 to Kyle.
Personally I was seeing many places that uses JRE 7, and some places even
uses JRE 6 yet.
Let's keep JDK 7 compatible, but borrow JDK 1.8's interface so that we can
easily migrate later.
Thanks,
Jungtaek Lim (HeartSaVioR)
On Tue, Jan 12, 2016 at 8:43 AM, P. Taylor Goetz <pt...@gmail.com> wrote:
> +1 for Derek and Kyle's comments.
>
> I think it's important to keep at least one level of JVM backward
> compatibility. I would love to dive straight in to JDK 1.8+, but that would
> be at the expense of users who may have infrastructure constraints that
> would prevent that.
>
> As mentioned earlier it is possible to mimick those features and APIs, and
> help pave the way for migration later. I'd be +1 for that approach.
>
> -Taylor
>
> > On Jan 11, 2016, at 5:56 PM, Kyle Nusbaum <kn...@yahoo-inc.com.INVALID>
> wrote:
> >
> > I agree with Derek.
> > There are still a lot of people using Java 7. However, if you could make
> it sort of Java 8 compatible so that when we do move to Java 8 we can do so
> with relative ease.
> > -- Kyle
> >
> > On Monday, January 11, 2016 4:46 PM, Derek Dagit
> <de...@yahoo-inc.com.INVALID> wrote:
> >
> >
> > I am not sure it makes sense to move to Java 8 merely because of the
> clojure->java translation, but it might be good timing so I would be OK
> with it.
> >
> > --
> > Derek
> >
> >
> > ----- Original Message -----
> > From: Reza Farivar <rf...@yahoo-inc.com.INVALID>
> > To: Dev <de...@storm.apache.org>
> > Sent: Monday, January 11, 2016 4:40 PM
> > Subject: Java 8 for Storm 2.x?
> >
> > I have started work on translating the util.clj to java (STORM-1226). I
> see some instances when translating the functional behavior of clojure to
> Java requires code that is already part of java 8.
> > For instance, there are many cases where a predicate function is passed
> around (e.g. in find-first). I can go ahead and implement a Predicate
> interface and use that, but Java 8 has already exactly that functionality
> implemented.
> > Would it make sense to move to Java 8 for the post-clojure branch 2.x?
> > --Reza
> >
> >
>
--
Name : Jungtaek Lim
Blog : http://medium.com/@heartsavior
Twitter : http://twitter.com/heartsavior
LinkedIn : http://www.linkedin.com/in/heartsavior
Re: Java 8 for Storm 2.x?
Posted by Jungtaek Lim <ka...@gmail.com>.
+1 to Kyle.
Personally I was seeing many places that uses JRE 7, and some places even
uses JRE 6 yet.
Let's keep JDK 7 compatible, but borrow JDK 1.8's interface so that we can
easily migrate later.
Thanks,
Jungtaek Lim (HeartSaVioR)
On Tue, Jan 12, 2016 at 8:43 AM, P. Taylor Goetz <pt...@gmail.com> wrote:
> +1 for Derek and Kyle's comments.
>
> I think it's important to keep at least one level of JVM backward
> compatibility. I would love to dive straight in to JDK 1.8+, but that would
> be at the expense of users who may have infrastructure constraints that
> would prevent that.
>
> As mentioned earlier it is possible to mimick those features and APIs, and
> help pave the way for migration later. I'd be +1 for that approach.
>
> -Taylor
>
> > On Jan 11, 2016, at 5:56 PM, Kyle Nusbaum <kn...@yahoo-inc.com.INVALID>
> wrote:
> >
> > I agree with Derek.
> > There are still a lot of people using Java 7. However, if you could make
> it sort of Java 8 compatible so that when we do move to Java 8 we can do so
> with relative ease.
> > -- Kyle
> >
> > On Monday, January 11, 2016 4:46 PM, Derek Dagit
> <de...@yahoo-inc.com.INVALID> wrote:
> >
> >
> > I am not sure it makes sense to move to Java 8 merely because of the
> clojure->java translation, but it might be good timing so I would be OK
> with it.
> >
> > --
> > Derek
> >
> >
> > ----- Original Message -----
> > From: Reza Farivar <rf...@yahoo-inc.com.INVALID>
> > To: Dev <de...@storm.apache.org>
> > Sent: Monday, January 11, 2016 4:40 PM
> > Subject: Java 8 for Storm 2.x?
> >
> > I have started work on translating the util.clj to java (STORM-1226). I
> see some instances when translating the functional behavior of clojure to
> Java requires code that is already part of java 8.
> > For instance, there are many cases where a predicate function is passed
> around (e.g. in find-first). I can go ahead and implement a Predicate
> interface and use that, but Java 8 has already exactly that functionality
> implemented.
> > Would it make sense to move to Java 8 for the post-clojure branch 2.x?
> > --Reza
> >
> >
>
--
Name : Jungtaek Lim
Blog : http://medium.com/@heartsavior
Twitter : http://twitter.com/heartsavior
LinkedIn : http://www.linkedin.com/in/heartsavior
Re: Java 8 for Storm 2.x?
Posted by "P. Taylor Goetz" <pt...@gmail.com>.
+1 for Derek and Kyle's comments.
I think it's important to keep at least one level of JVM backward compatibility. I would love to dive straight in to JDK 1.8+, but that would be at the expense of users who may have infrastructure constraints that would prevent that.
As mentioned earlier it is possible to mimick those features and APIs, and help pave the way for migration later. I'd be +1 for that approach.
-Taylor
> On Jan 11, 2016, at 5:56 PM, Kyle Nusbaum <kn...@yahoo-inc.com.INVALID> wrote:
>
> I agree with Derek.
> There are still a lot of people using Java 7. However, if you could make it sort of Java 8 compatible so that when we do move to Java 8 we can do so with relative ease.
> -- Kyle
>
> On Monday, January 11, 2016 4:46 PM, Derek Dagit <de...@yahoo-inc.com.INVALID> wrote:
>
>
> I am not sure it makes sense to move to Java 8 merely because of the clojure->java translation, but it might be good timing so I would be OK with it.
>
> --
> Derek
>
>
> ----- Original Message -----
> From: Reza Farivar <rf...@yahoo-inc.com.INVALID>
> To: Dev <de...@storm.apache.org>
> Sent: Monday, January 11, 2016 4:40 PM
> Subject: Java 8 for Storm 2.x?
>
> I have started work on translating the util.clj to java (STORM-1226). I see some instances when translating the functional behavior of clojure to Java requires code that is already part of java 8.
> For instance, there are many cases where a predicate function is passed around (e.g. in find-first). I can go ahead and implement a Predicate interface and use that, but Java 8 has already exactly that functionality implemented.
> Would it make sense to move to Java 8 for the post-clojure branch 2.x?
> --Reza
>
>
Re: Java 8 for Storm 2.x?
Posted by Kyle Nusbaum <kn...@yahoo-inc.com.INVALID>.
I agree with Derek.
There are still a lot of people using Java 7. However, if you could make it sort of Java 8 compatible so that when we do move to Java 8 we can do so with relative ease.
-- Kyle
On Monday, January 11, 2016 4:46 PM, Derek Dagit <de...@yahoo-inc.com.INVALID> wrote:
I am not sure it makes sense to move to Java 8 merely because of the clojure->java translation, but it might be good timing so I would be OK with it.
--
Derek
----- Original Message -----
From: Reza Farivar <rf...@yahoo-inc.com.INVALID>
To: Dev <de...@storm.apache.org>
Sent: Monday, January 11, 2016 4:40 PM
Subject: Java 8 for Storm 2.x?
I have started work on translating the util.clj to java (STORM-1226). I see some instances when translating the functional behavior of clojure to Java requires code that is already part of java 8.
For instance, there are many cases where a predicate function is passed around (e.g. in find-first). I can go ahead and implement a Predicate interface and use that, but Java 8 has already exactly that functionality implemented.
Would it make sense to move to Java 8 for the post-clojure branch 2.x?
--Reza
Re: Java 8 for Storm 2.x?
Posted by Derek Dagit <de...@yahoo-inc.com.INVALID>.
I am not sure it makes sense to move to Java 8 merely because of the clojure->java translation, but it might be good timing so I would be OK with it.
--
Derek
----- Original Message -----
From: Reza Farivar <rf...@yahoo-inc.com.INVALID>
To: Dev <de...@storm.apache.org>
Sent: Monday, January 11, 2016 4:40 PM
Subject: Java 8 for Storm 2.x?
I have started work on translating the util.clj to java (STORM-1226). I see some instances when translating the functional behavior of clojure to Java requires code that is already part of java 8.
For instance, there are many cases where a predicate function is passed around (e.g. in find-first). I can go ahead and implement a Predicate interface and use that, but Java 8 has already exactly that functionality implemented.
Would it make sense to move to Java 8 for the post-clojure branch 2.x?
--Reza