samza-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Riccomini <criccom...@apache.org>
Subject Re: [DISCUSS] JDK7
Date Wed, 18 Feb 2015 18:01:59 GMT
Hey all,

FYI- Calcite and Hive have also dropped support for JDK6:

  https://issues.apache.org/jira/browse/CALCITE-591
  https://issues.apache.org/jira/browse/HIVE-9521

This will impact SAMZA-390.

Cheers,
Chris

On Wed, Feb 18, 2015 at 9:40 AM, Chris Riccomini <criccomini@apache.org>
wrote:

> Hey all,
>
> Ruslan has been working on upgrading Samza to the latest RocksDB build.
>
>   https://issues.apache.org/jira/browse/SAMZA-442
>
> During this migration, we realized that upgrading Samza to a modern
> version of RocksDB will require JDK 7, since RocksDB requires it to build.
> Without this upgrade, we will not be able to take in TTL support in
> RocksDB, as well as any new features they release.
>
> Hadoop 2.7 (YARN) will also begin a vote in several weeks. This version
> mandates JDK7 be used at compile time:
>
>   https://issues.apache.org/jira/browse/HADOOP-10530
>
> Scala 2.11 requires JDK7+ transitively for us, since Scalatra 2.3 is built
> against JDK 7.
>
>   https://issues.apache.org/jira/browse/SAMZA-469
>
> We also discussed migrating to JDK 7 here:
>
>   https://issues.apache.org/jira/browse/SAMZA-455
>
> And here:
>
>
> http://mail-archives.apache.org/mod_mbox/incubator-samza-dev/201412.mbox/%3CD0AC655A.38469%25criccomini@linkedin.com%3E
>
> Taken in isolation, each one of these is potentially fixable. We could try
> and convince the RocksDB community to move back to JDK 6. We could punt on
> upgrading YARN for a year or more. The same goes for Scala 2.11. This
> doesn't seem ideal, and it's just going to get worse.
>
> I propose that we keep 0.9.0 on JDK6 and require JDK7 for 0.10.0. We can
> target an 0.9.0 release for March, and an 0.10.0 release for June. If we
> move to a more aggressive release schedule (e.g. monthly), then we'll
> require the JDK7 migration at the June release (but no earlier).
>
> Cheers,
> Chris
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message