[DISCUSS] Bump the minimum Java requirement to Java 7 for Flink

[Henry Saputra]

HI Guys,

I am wondering what do you guys think if we make Flink requires Java7
for both compile and runtime?

Several reasons why I am proposing this:
1. Java6 has reached end of life as announced by Oracle. We have seen
compile error happening with some versions of Java 6
2. Flink is just starting and hence have more flexibility to move to Java 7
3. Flink does not have compile dependencies that requires Java 6
4. Java 7 enhancements:
http://www.oracle.com/technetwork/java/javase/jdk7-relnotes-418459.html


Let me know what do you guys think.

- Henry

[Mohit Singh]

While I just just joined the community, so I am yet to be aware of the
internals of Flink but I am already liking the feature enhancements in Java
7 (type inferences, try-with-resources, diamond operator comes to my mind).

A digressing question, and I am sure this has would have been debated
extensively so pardon for bringing this up again.., but how did we chose
between java and scala?


On Wed, Oct 22, 2014 at 10:53 AM, Henry Saputra <[hidden email]>
wrote:

> HI Guys,
>
> I am wondering what do you guys think if we make Flink requires Java7
> for both compile and runtime?
>
> Several reasons why I am proposing this:
> 1. Java6 has reached end of life as announced by Oracle. We have seen
> compile error happening with some versions of Java 6
> 2. Flink is just starting and hence have more flexibility to move to Java 7
> 3. Flink does not have compile dependencies that requires Java 6
> 4. Java 7 enhancements:
> http://www.oracle.com/technetwork/java/javase/jdk7-relnotes-418459.html
>
>
> Let me know what do you guys think.
>
> - Henry
>

--
Mohit

"When you want success as badly as you want the air, then you will get it.
There is no other secret of success."
-Socrates

[Aljoscha Krettek-2]

One of the reasons is that Scala was not very well known when the
project started. That was around 2009. (Correct me if I'm wrong here,
please) The more important reason is that we try to have efficient
algorithms and memory management. This is easier to achieve in a
language like Java that is relatively low-level compared to Scala.
Scala makes it easy to write concise code that get's compiled to
inefficient code.

just my 2 cents...

On Wed, Oct 22, 2014 at 9:23 PM, Mohit Singh <[hidden email]> wrote:

> While I just just joined the community, so I am yet to be aware of the
> internals of Flink but I am already liking the feature enhancements in Java
> 7 (type inferences, try-with-resources, diamond operator comes to my mind).
>
> A digressing question, and I am sure this has would have been debated
> extensively so pardon for bringing this up again.., but how did we chose
> between java and scala?
>
>
> On Wed, Oct 22, 2014 at 10:53 AM, Henry Saputra <[hidden email]>
> wrote:
>
>> HI Guys,
>>
>> I am wondering what do you guys think if we make Flink requires Java7
>> for both compile and runtime?
>>
>> Several reasons why I am proposing this:
>> 1. Java6 has reached end of life as announced by Oracle. We have seen
>> compile error happening with some versions of Java 6
>> 2. Flink is just starting and hence have more flexibility to move to Java 7
>> 3. Flink does not have compile dependencies that requires Java 6
>> 4. Java 7 enhancements:
>> http://www.oracle.com/technetwork/java/javase/jdk7-relnotes-418459.html
>>
>>
>> Let me know what do you guys think.
>>
>> - Henry
>>
>
>
>
> --
> Mohit
>
> "When you want success as badly as you want the air, then you will get it.
> There is no other secret of success."
> -Socrates

[Daniel Warneke]

Hi,

I would also be in favor of dropping Java 6 support. In my opinion, Java
7 is the standard these days. All of the three big Hadoop distributions
also already consider Java 6 as deprecated for their latest releases
[1,2,3].

Best regards,

     Daniel

[1]
http://www.cloudera.com/content/cloudera/en/documentation/cdh5/latest/CDH5-Requirements-and-Supported-Versions/cdhrsv_jdk.html
[2] http://doc.mapr.com/display/MapR/JDK+Support+Matrix
[3]
http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.1-latest/bk_installing_manually_book/content/rpm-chap1-2.html#rpm-chap1-2-3

Am 22.10.2014 21:35, schrieb Aljoscha Krettek:

> One of the reasons is that Scala was not very well known when the
> project started. That was around 2009. (Correct me if I'm wrong here,
> please) The more important reason is that we try to have efficient
> algorithms and memory management. This is easier to achieve in a
> language like Java that is relatively low-level compared to Scala.
> Scala makes it easy to write concise code that get's compiled to
> inefficient code.
>
> just my 2 cents...
>
> On Wed, Oct 22, 2014 at 9:23 PM, Mohit Singh <[hidden email]> wrote:
>> While I just just joined the community, so I am yet to be aware of the
>> internals of Flink but I am already liking the feature enhancements in Java
>> 7 (type inferences, try-with-resources, diamond operator comes to my mind).
>>
>> A digressing question, and I am sure this has would have been debated
>> extensively so pardon for bringing this up again.., but how did we chose
>> between java and scala?
>>
>>
>> On Wed, Oct 22, 2014 at 10:53 AM, Henry Saputra <[hidden email]>
>> wrote:
>>
>>> HI Guys,
>>>
>>> I am wondering what do you guys think if we make Flink requires Java7
>>> for both compile and runtime?
>>>
>>> Several reasons why I am proposing this:
>>> 1. Java6 has reached end of life as announced by Oracle. We have seen
>>> compile error happening with some versions of Java 6
>>> 2. Flink is just starting and hence have more flexibility to move to Java 7
>>> 3. Flink does not have compile dependencies that requires Java 6
>>> 4. Java 7 enhancements:
>>> http://www.oracle.com/technetwork/java/javase/jdk7-relnotes-418459.html
>>>
>>>
>>> Let me know what do you guys think.
>>>
>>> - Henry
>>>
>>
>>
>> --
>> Mohit
>>
>> "When you want success as badly as you want the air, then you will get it.
>> There is no other secret of success."
>> -Socrates

[Stephan Ewen]

I know of a few companies who made the move away from java 6 just in the
last weeks or months.

I would vote to delay the bump till end of the year.
Am 22.10.2014 22:39 schrieb "Daniel Warneke" <[hidden email]>:

> Hi,
>
> I would also be in favor of dropping Java 6 support. In my opinion, Java 7
> is the standard these days. All of the three big Hadoop distributions also
> already consider Java 6 as deprecated for their latest releases [1,2,3].
>
> Best regards,
>
>     Daniel
>
> [1] http://www.cloudera.com/content/cloudera/en/documentation/cdh5/latest/
> CDH5-Requirements-and-Supported-Versions/cdhrsv_jdk.html
> [2] http://doc.mapr.com/display/MapR/JDK+Support+Matrix
> [3] http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.1-
> latest/bk_installing_manually_book/content/rpm-chap1-2.html#rpm-chap1-2-3
>
> Am 22.10.2014 21:35, schrieb Aljoscha Krettek:
>
>> One of the reasons is that Scala was not very well known when the
>> project started. That was around 2009. (Correct me if I'm wrong here,
>> please) The more important reason is that we try to have efficient
>> algorithms and memory management. This is easier to achieve in a
>> language like Java that is relatively low-level compared to Scala.
>> Scala makes it easy to write concise code that get's compiled to
>> inefficient code.
>>
>> just my 2 cents...
>>
>> On Wed, Oct 22, 2014 at 9:23 PM, Mohit Singh <[hidden email]> wrote:
>>
>>> While I just just joined the community, so I am yet to be aware of the
>>> internals of Flink but I am already liking the feature enhancements in
>>> Java
>>> 7 (type inferences, try-with-resources, diamond operator comes to my
>>> mind).
>>>
>>> A digressing question, and I am sure this has would have been debated
>>> extensively so pardon for bringing this up again.., but how did we chose
>>> between java and scala?
>>>
>>>
>>> On Wed, Oct 22, 2014 at 10:53 AM, Henry Saputra <[hidden email]
>>> >
>>> wrote:
>>>
>>>  HI Guys,
>>>>
>>>> I am wondering what do you guys think if we make Flink requires Java7
>>>> for both compile and runtime?
>>>>
>>>> Several reasons why I am proposing this:
>>>> 1. Java6 has reached end of life as announced by Oracle. We have seen
>>>> compile error happening with some versions of Java 6
>>>> 2. Flink is just starting and hence have more flexibility to move to
>>>> Java 7
>>>> 3. Flink does not have compile dependencies that requires Java 6
>>>> 4. Java 7 enhancements:
>>>> http://www.oracle.com/technetwork/java/javase/jdk7-relnotes-418459.html
>>>>
>>>>
>>>> Let me know what do you guys think.
>>>>
>>>> - Henry
>>>>
>>>>
>>>
>>> --
>>> Mohit
>>>
>>> "When you want success as badly as you want the air, then you will get
>>> it.
>>> There is no other secret of success."
>>> -Socrates
>>>
>>
>

[Henry Saputra]

Also just saw that Java 7 EOL is in about 6 months [1]


[1] http://www.oracle.com/technetwork/java/eol-135779.html

On Thu, Oct 23, 2014 at 5:03 AM, Stephan Ewen <[hidden email]> wrote:

> I know of a few companies who made the move away from java 6 just in the
> last weeks or months.
>
> I would vote to delay the bump till end of the year.
> Am 22.10.2014 22:39 schrieb "Daniel Warneke" <[hidden email]>:
>
>> Hi,
>>
>> I would also be in favor of dropping Java 6 support. In my opinion, Java 7
>> is the standard these days. All of the three big Hadoop distributions also
>> already consider Java 6 as deprecated for their latest releases [1,2,3].
>>
>> Best regards,
>>
>>     Daniel
>>
>> [1] http://www.cloudera.com/content/cloudera/en/documentation/cdh5/latest/
>> CDH5-Requirements-and-Supported-Versions/cdhrsv_jdk.html
>> [2] http://doc.mapr.com/display/MapR/JDK+Support+Matrix
>> [3] http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.1-
>> latest/bk_installing_manually_book/content/rpm-chap1-2.html#rpm-chap1-2-3
>>
>> Am 22.10.2014 21:35, schrieb Aljoscha Krettek:
>>
>>> One of the reasons is that Scala was not very well known when the
>>> project started. That was around 2009. (Correct me if I'm wrong here,
>>> please) The more important reason is that we try to have efficient
>>> algorithms and memory management. This is easier to achieve in a
>>> language like Java that is relatively low-level compared to Scala.
>>> Scala makes it easy to write concise code that get's compiled to
>>> inefficient code.
>>>
>>> just my 2 cents...
>>>
>>> On Wed, Oct 22, 2014 at 9:23 PM, Mohit Singh <[hidden email]> wrote:
>>>
>>>> While I just just joined the community, so I am yet to be aware of the
>>>> internals of Flink but I am already liking the feature enhancements in
>>>> Java
>>>> 7 (type inferences, try-with-resources, diamond operator comes to my
>>>> mind).
>>>>
>>>> A digressing question, and I am sure this has would have been debated
>>>> extensively so pardon for bringing this up again.., but how did we chose
>>>> between java and scala?
>>>>
>>>>
>>>> On Wed, Oct 22, 2014 at 10:53 AM, Henry Saputra <[hidden email]
>>>> >
>>>> wrote:
>>>>
>>>>  HI Guys,
>>>>>
>>>>> I am wondering what do you guys think if we make Flink requires Java7
>>>>> for both compile and runtime?
>>>>>
>>>>> Several reasons why I am proposing this:
>>>>> 1. Java6 has reached end of life as announced by Oracle. We have seen
>>>>> compile error happening with some versions of Java 6
>>>>> 2. Flink is just starting and hence have more flexibility to move to
>>>>> Java 7
>>>>> 3. Flink does not have compile dependencies that requires Java 6
>>>>> 4. Java 7 enhancements:
>>>>> http://www.oracle.com/technetwork/java/javase/jdk7-relnotes-418459.html
>>>>>
>>>>>
>>>>> Let me know what do you guys think.
>>>>>
>>>>> - Henry
>>>>>
>>>>>
>>>>
>>>> --
>>>> Mohit
>>>>
>>>> "When you want success as badly as you want the air, then you will get
>>>> it.
>>>> There is no other secret of success."
>>>> -Socrates
>>>>
>>>
>>

[Robert Metzger]

I personally think that one of the most important goals of our project is
to get new users trying it out. Therefore, we need to avoid any possible
entry barrier.
Sadly, it seems that people (in particular companies) are still using Java
6, even though its not being maintained anymore and potentially insecure.
I don't think our project is in a position to convince people (again,
companies ;) ) to switch to a more up-to-date java version. The thing with
Java 6 is kind of a chicken-and-egg dilemma and in an ideal world, we
should make a bold move to finally get rid of java 6.

I would suggest to add a little check to the JobManager startup process and
print a WARN message for Java 6 users, that we are planning to drop Java 6
support soon. This way, we allow Java 6 user to try out Flink and at the
same time give them another reason to move to 7.


On Fri, Oct 24, 2014 at 9:07 PM, Henry Saputra <[hidden email]>
wrote:

> Also just saw that Java 7 EOL is in about 6 months [1]
>
>
> [1] http://www.oracle.com/technetwork/java/eol-135779.html
>
> On Thu, Oct 23, 2014 at 5:03 AM, Stephan Ewen <[hidden email]> wrote:
> > I know of a few companies who made the move away from java 6 just in the
> > last weeks or months.
> >
> > I would vote to delay the bump till end of the year.
> > Am 22.10.2014 22:39 schrieb "Daniel Warneke" <[hidden email]>:
> >
> >> Hi,
> >>
> >> I would also be in favor of dropping Java 6 support. In my opinion,
> Java 7
> >> is the standard these days. All of the three big Hadoop distributions
> also
> >> already consider Java 6 as deprecated for their latest releases [1,2,3].
> >>
> >> Best regards,
> >>
> >>     Daniel
> >>
> >> [1]
> http://www.cloudera.com/content/cloudera/en/documentation/cdh5/latest/
> >> CDH5-Requirements-and-Supported-Versions/cdhrsv_jdk.html
> >> [2] http://doc.mapr.com/display/MapR/JDK+Support+Matrix
> >> [3] http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.1-
> >>
> latest/bk_installing_manually_book/content/rpm-chap1-2.html#rpm-chap1-2-3
> >>
> >> Am 22.10.2014 21:35, schrieb Aljoscha Krettek:
> >>
> >>> One of the reasons is that Scala was not very well known when the
> >>> project started. That was around 2009. (Correct me if I'm wrong here,
> >>> please) The more important reason is that we try to have efficient
> >>> algorithms and memory management. This is easier to achieve in a
> >>> language like Java that is relatively low-level compared to Scala.
> >>> Scala makes it easy to write concise code that get's compiled to
> >>> inefficient code.
> >>>
> >>> just my 2 cents...
> >>>
> >>> On Wed, Oct 22, 2014 at 9:23 PM, Mohit Singh <[hidden email]>
> wrote:
> >>>
> >>>> While I just just joined the community, so I am yet to be aware of the
> >>>> internals of Flink but I am already liking the feature enhancements in
> >>>> Java
> >>>> 7 (type inferences, try-with-resources, diamond operator comes to my
> >>>> mind).
> >>>>
> >>>> A digressing question, and I am sure this has would have been debated
> >>>> extensively so pardon for bringing this up again.., but how did we
> chose
> >>>> between java and scala?
> >>>>
> >>>>
> >>>> On Wed, Oct 22, 2014 at 10:53 AM, Henry Saputra <
> [hidden email]
> >>>> >
> >>>> wrote:
> >>>>
> >>>>  HI Guys,
> >>>>>
> >>>>> I am wondering what do you guys think if we make Flink requires Java7
> >>>>> for both compile and runtime?
> >>>>>
> >>>>> Several reasons why I am proposing this:
> >>>>> 1. Java6 has reached end of life as announced by Oracle. We have seen
> >>>>> compile error happening with some versions of Java 6
> >>>>> 2. Flink is just starting and hence have more flexibility to move to
> >>>>> Java 7
> >>>>> 3. Flink does not have compile dependencies that requires Java 6
> >>>>> 4. Java 7 enhancements:
> >>>>>
> http://www.oracle.com/technetwork/java/javase/jdk7-relnotes-418459.html
> >>>>>
> >>>>>
> >>>>> Let me know what do you guys think.
> >>>>>
> >>>>> - Henry
> >>>>>
> >>>>>
> >>>>
> >>>> --
> >>>> Mohit
> >>>>
> >>>> "When you want success as badly as you want the air, then you will get
> >>>> it.
> >>>> There is no other secret of success."
> >>>> -Socrates
> >>>>
> >>>
> >>
>

[Aljoscha Krettek-2]

Yes, I like that idea.

On Sun, Oct 26, 2014 at 9:10 AM, Robert Metzger <[hidden email]> wrote:

> I personally think that one of the most important goals of our project is
> to get new users trying it out. Therefore, we need to avoid any possible
> entry barrier.
> Sadly, it seems that people (in particular companies) are still using Java
> 6, even though its not being maintained anymore and potentially insecure.
> I don't think our project is in a position to convince people (again,
> companies ;) ) to switch to a more up-to-date java version. The thing with
> Java 6 is kind of a chicken-and-egg dilemma and in an ideal world, we
> should make a bold move to finally get rid of java 6.
>
> I would suggest to add a little check to the JobManager startup process and
> print a WARN message for Java 6 users, that we are planning to drop Java 6
> support soon. This way, we allow Java 6 user to try out Flink and at the
> same time give them another reason to move to 7.
>
>
> On Fri, Oct 24, 2014 at 9:07 PM, Henry Saputra <[hidden email]>
> wrote:
>
>> Also just saw that Java 7 EOL is in about 6 months [1]
>>
>>
>> [1] http://www.oracle.com/technetwork/java/eol-135779.html
>>
>> On Thu, Oct 23, 2014 at 5:03 AM, Stephan Ewen <[hidden email]> wrote:
>> > I know of a few companies who made the move away from java 6 just in the
>> > last weeks or months.
>> >
>> > I would vote to delay the bump till end of the year.
>> > Am 22.10.2014 22:39 schrieb "Daniel Warneke" <[hidden email]>:
>> >
>> >> Hi,
>> >>
>> >> I would also be in favor of dropping Java 6 support. In my opinion,
>> Java 7
>> >> is the standard these days. All of the three big Hadoop distributions
>> also
>> >> already consider Java 6 as deprecated for their latest releases [1,2,3].
>> >>
>> >> Best regards,
>> >>
>> >>     Daniel
>> >>
>> >> [1]
>> http://www.cloudera.com/content/cloudera/en/documentation/cdh5/latest/
>> >> CDH5-Requirements-and-Supported-Versions/cdhrsv_jdk.html
>> >> [2] http://doc.mapr.com/display/MapR/JDK+Support+Matrix
>> >> [3] http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.1-
>> >>
>> latest/bk_installing_manually_book/content/rpm-chap1-2.html#rpm-chap1-2-3
>> >>
>> >> Am 22.10.2014 21:35, schrieb Aljoscha Krettek:
>> >>
>> >>> One of the reasons is that Scala was not very well known when the
>> >>> project started. That was around 2009. (Correct me if I'm wrong here,
>> >>> please) The more important reason is that we try to have efficient
>> >>> algorithms and memory management. This is easier to achieve in a
>> >>> language like Java that is relatively low-level compared to Scala.
>> >>> Scala makes it easy to write concise code that get's compiled to
>> >>> inefficient code.
>> >>>
>> >>> just my 2 cents...
>> >>>
>> >>> On Wed, Oct 22, 2014 at 9:23 PM, Mohit Singh <[hidden email]>
>> wrote:
>> >>>
>> >>>> While I just just joined the community, so I am yet to be aware of the
>> >>>> internals of Flink but I am already liking the feature enhancements in
>> >>>> Java
>> >>>> 7 (type inferences, try-with-resources, diamond operator comes to my
>> >>>> mind).
>> >>>>
>> >>>> A digressing question, and I am sure this has would have been debated
>> >>>> extensively so pardon for bringing this up again.., but how did we
>> chose
>> >>>> between java and scala?
>> >>>>
>> >>>>
>> >>>> On Wed, Oct 22, 2014 at 10:53 AM, Henry Saputra <
>> [hidden email]
>> >>>> >
>> >>>> wrote:
>> >>>>
>> >>>>  HI Guys,
>> >>>>>
>> >>>>> I am wondering what do you guys think if we make Flink requires Java7
>> >>>>> for both compile and runtime?
>> >>>>>
>> >>>>> Several reasons why I am proposing this:
>> >>>>> 1. Java6 has reached end of life as announced by Oracle. We have seen
>> >>>>> compile error happening with some versions of Java 6
>> >>>>> 2. Flink is just starting and hence have more flexibility to move to
>> >>>>> Java 7
>> >>>>> 3. Flink does not have compile dependencies that requires Java 6
>> >>>>> 4. Java 7 enhancements:
>> >>>>>
>> http://www.oracle.com/technetwork/java/javase/jdk7-relnotes-418459.html
>> >>>>>
>> >>>>>
>> >>>>> Let me know what do you guys think.
>> >>>>>
>> >>>>> - Henry
>> >>>>>
>> >>>>>
>> >>>>
>> >>>> --
>> >>>> Mohit
>> >>>>
>> >>>> "When you want success as badly as you want the air, then you will get
>> >>>> it.
>> >>>> There is no other secret of success."
>> >>>> -Socrates
>> >>>>
>> >>>
>> >>
>>

[Chiwan Park]

I think that’s good idea!

—
Chiwan Park (Sent with iPhone)

> On Oct 26, 2014, at 5:10 PM, Robert Metzger <[hidden email]> wrote:
>
> I personally think that one of the most important goals of our project is
> to get new users trying it out. Therefore, we need to avoid any possible
> entry barrier.
> Sadly, it seems that people (in particular companies) are still using Java
> 6, even though its not being maintained anymore and potentially insecure.
> I don't think our project is in a position to convince people (again,
> companies ;) ) to switch to a more up-to-date java version. The thing with
> Java 6 is kind of a chicken-and-egg dilemma and in an ideal world, we
> should make a bold move to finally get rid of java 6.
>
> I would suggest to add a little check to the JobManager startup process and
> print a WARN message for Java 6 users, that we are planning to drop Java 6
> support soon. This way, we allow Java 6 user to try out Flink and at the
> same time give them another reason to move to 7.
>
>
> On Fri, Oct 24, 2014 at 9:07 PM, Henry Saputra <[hidden email]>
> wrote:
>
>> Also just saw that Java 7 EOL is in about 6 months [1]
>>
>>
>> [1] http://www.oracle.com/technetwork/java/eol-135779.html
>>
>> On Thu, Oct 23, 2014 at 5:03 AM, Stephan Ewen <[hidden email]> wrote:
>>> I know of a few companies who made the move away from java 6 just in the
>>> last weeks or months.
>>>
>>> I would vote to delay the bump till end of the year.
>>> Am 22.10.2014 22:39 schrieb "Daniel Warneke" <[hidden email]>:
>>>
>>>> Hi,
>>>>
>>>> I would also be in favor of dropping Java 6 support. In my opinion,
>> Java 7
>>>> is the standard these days. All of the three big Hadoop distributions
>> also
>>>> already consider Java 6 as deprecated for their latest releases [1,2,3].
>>>>
>>>> Best regards,
>>>>
>>>>    Daniel
>>>>
>>>> [1]
>> http://www.cloudera.com/content/cloudera/en/documentation/cdh5/latest/
>>>> CDH5-Requirements-and-Supported-Versions/cdhrsv_jdk.html
>>>> [2] http://doc.mapr.com/display/MapR/JDK+Support+Matrix
>>>> [3] http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.1-
>>>>
>> latest/bk_installing_manually_book/content/rpm-chap1-2.html#rpm-chap1-2-3
>>>>
>>>> Am 22.10.2014 21:35, schrieb Aljoscha Krettek:
>>>>
>>>>> One of the reasons is that Scala was not very well known when the
>>>>> project started. That was around 2009. (Correct me if I'm wrong here,
>>>>> please) The more important reason is that we try to have efficient
>>>>> algorithms and memory management. This is easier to achieve in a
>>>>> language like Java that is relatively low-level compared to Scala.
>>>>> Scala makes it easy to write concise code that get's compiled to
>>>>> inefficient code.
>>>>>
>>>>> just my 2 cents...
>>>>>
>>>>> On Wed, Oct 22, 2014 at 9:23 PM, Mohit Singh <[hidden email]>
>> wrote:
>>>>>
>>>>>> While I just just joined the community, so I am yet to be aware of the
>>>>>> internals of Flink but I am already liking the feature enhancements in
>>>>>> Java
>>>>>> 7 (type inferences, try-with-resources, diamond operator comes to my
>>>>>> mind).
>>>>>>
>>>>>> A digressing question, and I am sure this has would have been debated
>>>>>> extensively so pardon for bringing this up again.., but how did we
>> chose
>>>>>> between java and scala?
>>>>>>
>>>>>>
>>>>>> On Wed, Oct 22, 2014 at 10:53 AM, Henry Saputra <
>> [hidden email]
>>>>>>>
>>>>>> wrote:
>>>>>>
>>>>>> HI Guys,
>>>>>>>
>>>>>>> I am wondering what do you guys think if we make Flink requires Java7
>>>>>>> for both compile and runtime?
>>>>>>>
>>>>>>> Several reasons why I am proposing this:
>>>>>>> 1. Java6 has reached end of life as announced by Oracle. We have seen
>>>>>>> compile error happening with some versions of Java 6
>>>>>>> 2. Flink is just starting and hence have more flexibility to move to
>>>>>>> Java 7
>>>>>>> 3. Flink does not have compile dependencies that requires Java 6
>>>>>>> 4. Java 7 enhancements:
>>>>>>>
>> http://www.oracle.com/technetwork/java/javase/jdk7-relnotes-418459.html
>>>>>>>
>>>>>>>
>>>>>>> Let me know what do you guys think.
>>>>>>>
>>>>>>> - Henry
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Mohit
>>>>>>
>>>>>> "When you want success as badly as you want the air, then you will get
>>>>>> it.
>>>>>> There is no other secret of success."
>>>>>> -Socrates
>>>>>>
>>>>>
>>>>
>>

[Henry Saputra]

Sounds good. I have file JIRA ticket to address this issue [1]

Thanks,

Henry

[1] https://issues.apache.org/jira/browse/FLINK-1183

On Sun, Oct 26, 2014 at 1:10 AM, Robert Metzger <[hidden email]> wrote:

> I personally think that one of the most important goals of our project is
> to get new users trying it out. Therefore, we need to avoid any possible
> entry barrier.
> Sadly, it seems that people (in particular companies) are still using Java
> 6, even though its not being maintained anymore and potentially insecure.
> I don't think our project is in a position to convince people (again,
> companies ;) ) to switch to a more up-to-date java version. The thing with
> Java 6 is kind of a chicken-and-egg dilemma and in an ideal world, we
> should make a bold move to finally get rid of java 6.
>
> I would suggest to add a little check to the JobManager startup process and
> print a WARN message for Java 6 users, that we are planning to drop Java 6
> support soon. This way, we allow Java 6 user to try out Flink and at the
> same time give them another reason to move to 7.
>
>
> On Fri, Oct 24, 2014 at 9:07 PM, Henry Saputra <[hidden email]>
> wrote:
>
>> Also just saw that Java 7 EOL is in about 6 months [1]
>>
>>
>> [1] http://www.oracle.com/technetwork/java/eol-135779.html
>>
>> On Thu, Oct 23, 2014 at 5:03 AM, Stephan Ewen <[hidden email]> wrote:
>> > I know of a few companies who made the move away from java 6 just in the
>> > last weeks or months.
>> >
>> > I would vote to delay the bump till end of the year.
>> > Am 22.10.2014 22:39 schrieb "Daniel Warneke" <[hidden email]>:
>> >
>> >> Hi,
>> >>
>> >> I would also be in favor of dropping Java 6 support. In my opinion,
>> Java 7
>> >> is the standard these days. All of the three big Hadoop distributions
>> also
>> >> already consider Java 6 as deprecated for their latest releases [1,2,3].
>> >>
>> >> Best regards,
>> >>
>> >>     Daniel
>> >>
>> >> [1]
>> http://www.cloudera.com/content/cloudera/en/documentation/cdh5/latest/
>> >> CDH5-Requirements-and-Supported-Versions/cdhrsv_jdk.html
>> >> [2] http://doc.mapr.com/display/MapR/JDK+Support+Matrix
>> >> [3] http://docs.hortonworks.com/HDPDocuments/HDP2/HDP-2.1-
>> >>
>> latest/bk_installing_manually_book/content/rpm-chap1-2.html#rpm-chap1-2-3
>> >>
>> >> Am 22.10.2014 21:35, schrieb Aljoscha Krettek:
>> >>
>> >>> One of the reasons is that Scala was not very well known when the
>> >>> project started. That was around 2009. (Correct me if I'm wrong here,
>> >>> please) The more important reason is that we try to have efficient
>> >>> algorithms and memory management. This is easier to achieve in a
>> >>> language like Java that is relatively low-level compared to Scala.
>> >>> Scala makes it easy to write concise code that get's compiled to
>> >>> inefficient code.
>> >>>
>> >>> just my 2 cents...
>> >>>
>> >>> On Wed, Oct 22, 2014 at 9:23 PM, Mohit Singh <[hidden email]>
>> wrote:
>> >>>
>> >>>> While I just just joined the community, so I am yet to be aware of the
>> >>>> internals of Flink but I am already liking the feature enhancements in
>> >>>> Java
>> >>>> 7 (type inferences, try-with-resources, diamond operator comes to my
>> >>>> mind).
>> >>>>
>> >>>> A digressing question, and I am sure this has would have been debated
>> >>>> extensively so pardon for bringing this up again.., but how did we
>> chose
>> >>>> between java and scala?
>> >>>>
>> >>>>
>> >>>> On Wed, Oct 22, 2014 at 10:53 AM, Henry Saputra <
>> [hidden email]
>> >>>> >
>> >>>> wrote:
>> >>>>
>> >>>>  HI Guys,
>> >>>>>
>> >>>>> I am wondering what do you guys think if we make Flink requires Java7
>> >>>>> for both compile and runtime?
>> >>>>>
>> >>>>> Several reasons why I am proposing this:
>> >>>>> 1. Java6 has reached end of life as announced by Oracle. We have seen
>> >>>>> compile error happening with some versions of Java 6
>> >>>>> 2. Flink is just starting and hence have more flexibility to move to
>> >>>>> Java 7
>> >>>>> 3. Flink does not have compile dependencies that requires Java 6
>> >>>>> 4. Java 7 enhancements:
>> >>>>>
>> http://www.oracle.com/technetwork/java/javase/jdk7-relnotes-418459.html
>> >>>>>
>> >>>>>
>> >>>>> Let me know what do you guys think.
>> >>>>>
>> >>>>> - Henry
>> >>>>>
>> >>>>>
>> >>>>
>> >>>> --
>> >>>> Mohit
>> >>>>
>> >>>> "When you want success as badly as you want the air, then you will get
>> >>>> it.
>> >>>> There is no other secret of success."
>> >>>> -Socrates
>> >>>>
>> >>>
>> >>
>>

[sirinath]

I think it is best to drop support a JVM when it reaches the end of life cycle or some time before reaching this date (when announcement is made). You can publish this as a policy so there is no surprises on the supported JVM version.

(Corrected some typos above)

[Stephan Ewen]

I think dropping support when a JVM reaches the end of the commercial
support is highly premature. As I said before, there are several examples
of companies are still (partly) on Java 6 or just made the switch to Java
7. Dropping support as early as Oracle means in practice shutting users out.

On Thu, Oct 30, 2014 at 5:52 AM, sirinath <[hidden email]> wrote:

> I think it is best to drop support a JVM when it reaches the end of life
> cycle or some time before reaching this date (when announcement is made).
> You can publish this as a policy so there is not surprises.
>
>
>
> --
> View this message in context:
> http://apache-flink-incubator-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Bump-the-minimum-Java-requirement-to-Java-7-for-Flink-tp2243p2297.html
> Sent from the Apache Flink (Incubator) Mailing List archive. mailing list
> archive at Nabble.com.
>