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 Mon, 02 Mar 2015 00:33:31 GMT
Hey all,

I posted a docs patch here:

  https://issues.apache.org/jira/browse/SAMZA-455

Cheers,
Chris

On Wed, Feb 25, 2015 at 11:28 AM, Chris Riccomini <criccomini@apache.org>
wrote:

> Hey all,
>
> It's been a week. I'm moving forward with this. I will open a JIRA to b
> clear about JDK support on the website.
>
> Cheers,
> Chris
>
> On Wed, Feb 18, 2015 at 11:00 AM, Tommy Becker <tobecker@tivo.com> wrote:
>
>> I just added this comment to SAMZA-455, since I was listed as requesting
>> JDK 6 support:
>>
>> We have recently migrated to JDK 8, so you may consider my request for
>> JDK 6 support withdrawn (though it was really more of a clarification of
>> whether JDK 6 is supported than a request for such support). Personally, I
>> feel that requiring JDK 7 is perfectly fine at this stage. Enterprise
>> customers will not move until projects start requiring it, so that argument
>> works both ways.
>>
>> ________________________________________
>> From: Julian Hyde [julian@hydromatic.net]
>> Sent: Wednesday, February 18, 2015 1:25 PM
>> To: dev@samza.apache.org
>> Subject: Re: [DISCUSS] JDK7
>>
>> Another data point. Calcite just dropped support for JDK 1.6. Calcite 1.0
>> supports 1.6, 1.7, 1.8, but Calcite 1.1 will only support 1.7, 1.8. We
>> could be persuaded to reconsider.
>>
>> Julian
>>
>> > On Feb 18, 2015, at 09:40, 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
>>
>> ________________________________
>>
>> This email and any attachments may contain confidential and privileged
>> material for the sole use of the intended recipient. Any review, copying,
>> or distribution of this email (or any attachments) by others is prohibited.
>> If you are not the intended recipient, please contact the sender
>> immediately and permanently delete this email and any attachments. No
>> employee or agent of TiVo Inc. is authorized to conclude any binding
>> agreement on behalf of TiVo Inc. by email. Binding agreements with TiVo
>> Inc. may only be made by a signed written agreement.
>>
>
>

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