Wow that’s an overwhelming support :)

I’ll keep the email thread open for few days to give possibility to others to 
chime in.

Jarcec

> On Jul 28, 2015, at 8:36 PM, Xu, Qian A <[email protected]> wrote:
> 
> +1
> 
> -----Original Message-----
> From: Zhou, Richard [mailto:[email protected]] 
> Sent: Wednesday, July 29, 2015 9:31 AM
> To: [email protected]
> Subject: RE: Dropping support for JDK6
> 
> +1
> 
> 
> Regards
> Richard
> 
> -----Original Message-----
> From: Abraham Elmahrek [mailto:[email protected]]
> Sent: Wednesday, July 29, 2015 5:07 AM
> To: [email protected]
> Subject: Re: Dropping support for JDK6
> 
> +1
> 
> On Tue, Jul 28, 2015 at 9:00 AM, Venkat Ranganathan < 
> [email protected]> wrote:
> 
>> +1
>> 
>> 
>> 
>> 
>> On 7/28/15, 8:24 AM, "Jarek Jarcec Cecho" <[email protected] on behalf 
>> of [email protected]> wrote:
>> 
>>> Hi All,
>>> JDK6 has been officially put end of life by Oracle more then 2 years 
>>> ago
>> (February 2013). Other projects in Hadoop ecosystems have already 
>> dropped
>> JDK6 support - for example Hadoop [1], HBase [2] or Pig[3] and hence I 
>> would like to kick off discussion to do the same in Sqoop as well.
>>> 
>>> What exactly that would mean for our users:
>>> * User would need to use at least JDK7 on the runtime - we’re 
>>> spawning
>> mapreduce job, so entire cluster would have to be running on at least
>> JDK7
>>> 
>>> What would that mean for Sqoop developers:
>>> * We would change our build scripts to use -source and -target 1.7 
>>> [4]
>> preventing the compilation with JDK6
>>> * We could use JDK7 specific language features in the source code [5]
>>> 
>>> What do you think?
>>> 
>>> Jarcec
>>> 
>>> Links:
>>> 1: http://markmail.org/thread/ytisa4w73ym4ee65
>>> 2: https://issues.apache.org/jira/browse/HBASE-11666
>>> 3: http://markmail.org/message/4pdyv22bimh5ae7n
>>> 4:
>> http://docs.oracle.com/javase/7/docs/technotes/tools/windows/javac.htm
>> l
>>> 5:
>> http://docs.oracle.com/javase/7/docs/technotes/guides/language/enhance
>> ments.html
>> 

Reply via email to