Also, we need to keep client side libraries (e.g., tajo-cli, tajo-client, and tajo-jdbc) jdk 7. If so, mybatis won't have any problem.
- hyunsik On Tue, May 26, 2015 at 4:19 AM, Hyunsik Choi <[email protected]> wrote: > In addition, hadoop stack is still on the JDK 7. But, Tajo can only > run in JDK8 with simply setting JAVA_HOME in tajo-env.sh. > > On Tue, May 26, 2015 at 4:17 AM, Hyunsik Choi <[email protected]> wrote: >> Thank you for your comments. We already have done all tests of Tajo in JDK8. >> https://builds.apache.org/job/Tajo-master-jdk8-nightly/ >> >> Your concern seems to be related to other third-party libraries which >> have problems in JDK8. Of course, we will have some staging period, >> allowing us to back to jdk 7. >> >> Best regards, >> Hyunsik >> >> On Tue, May 26, 2015 at 3:52 AM, CharSyam <[email protected]> wrote: >>> before it, we should check compatibility. >>> for example java 1.8 causes some problems with mybatis or json libraries >>> >>> 2015년 5월 26일 화요일, Hyunsik Choi<[email protected]>님이 작성한 메시지: >>> >>>> Hi folks, >>>> >>>> I'm going to discuss the migration of code base to Java 8 with >>>> skipping Java 7. Java 8 has many great features and improved >>>> performance. Also, Java 7 will reach April 2015 and Java 9 will be >>>> release in the next year. Java 8 is not early adopting anymore. In >>>> addition, as far as I know, Java 8 has already been used in many >>>> productions and also will be adopted in production soon in many >>>> companies. >>>> >>>> If possible, we can move 0.11 to Java 8 only or the next release after >>>> 0.11. >>>> >>>> How do you think about that? >>>> >>>> Best regards, >>>> Hyunsik >>>>
