Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Plain View
Accumulo >> mail # dev >> Re: [VOTE] JDK 1.7 - Switch for Accumulo 1.6.0


+
Keith Turner 2013-06-03, 22:05
+
Adam Fuchs 2013-06-03, 21:49
+
Christopher 2013-06-03, 22:10
+
Christopher 2013-06-03, 22:23
+
Sean Busbey 2013-06-03, 22:31
+
Christopher 2013-06-03, 22:39
+
William Slacum 2013-06-03, 22:31
+
Keith Turner 2013-06-03, 22:22
+
Christopher 2013-06-03, 22:15
+
Josh Elser 2013-06-03, 21:04
+
Josh Elser 2013-06-03, 22:01
+
Sean Busbey 2013-06-03, 23:05
Copy link to this message
-
RE: [VOTE] JDK 1.7 - Switch for Accumulo 1.6.0

 +1 with reservations. This seems like a big API change, not because our dependency changes, but doesn't it force all consumers to change to Java 7 as well if new language features are used in the client? Looks like Java 6 compiled iterators should work without change.

 I wonder if would make sense to:

 - move client to its own module (out of core),
 - build a Java 6 distribution of the client in addition to the Java 7 release, and
 - refrain from using Java 7 features in the client until a 2.0 release

-----Original Message-----
From: Sean Busbey [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 03, 2013 7:05 PM
To: [EMAIL PROTECTED]
Subject: Re: [VOTE] JDK 1.7 - Switch for Accumulo 1.6.0

On Mon, Jun 3, 2013 at 5:04 PM, Josh Elser <[EMAIL PROTECTED]> wrote:

> <snip>

Also, some quick searching leads me to believe that 1.6 bytecode will run
> on a 1.7 JVM, but not vice versa. Does anyone know if this is the
> case? I apologize if I'm bringing up an already-discussed subject.
> <snip>
>
Just to confirm, the JDK7 compatibility guide says JDK7 compiled code won't work on a Java 6 VM[1]:

> The class file version for Java SE 7 is 51, as per the JVM
> Specification,
because of the invokedynamic byte code
> introduced by JSR 292. Version 51 class files produced by the Java SE
> 7
compiler cannot be used in Java SE 6.

[1]:
http://www.oracle.com/technetwork/java/javase/compatibility-417013.html#binary

--
Sean
+
Josh Elser 2013-06-04, 01:05
+
Ben Popp 2013-06-04, 02:37
+
Sean Busbey 2013-06-04, 12:21
+
John Vines 2013-06-04, 14:51
+
Christopher 2013-06-05, 17:54
+
John Vines 2013-06-05, 18:14
+
Adam Fuchs 2013-06-05, 18:20
+
Eric Newton 2013-06-05, 20:36
+
Christopher 2013-06-05, 20:42
+
Josh Elser 2013-06-05, 23:09
+
Mike Drob 2013-06-05, 23:25
+
David Medinets 2013-06-05, 23:29
+
Mike Drob 2013-06-05, 23:28
+
John Vines 2013-06-05, 23:12
+
Keith Turner 2013-06-05, 23:54
+
John Vines 2013-06-05, 22:09
+
Jason Trost 2013-06-05, 22:48
+
Sean Busbey 2013-06-05, 18:12
+
German Gutierrez 2013-06-06, 02:53
+
David Lyle 2013-06-06, 03:51
+
David Medinets 2013-06-06, 13:52
+
Billie Rinaldi 2013-06-06, 14:22
+
Josh Elser 2013-06-06, 15:03
+
Christopher 2013-06-06, 18:09
+
Christopher 2013-06-07, 16:05
+
Sean Busbey 2013-06-06, 14:00
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB