Hi all, Would it be possible to consider including the following in the 0.11.0 target release?
SAMZA-855: Upgrade Samza's Kafka client version to 0.10.0.0 We are looking at upgrading our Kafka cluster to 0.10 and Samza is currently preventing us from doing so. Regards, Nicolas Maquet 2016-08-23 9:06 GMT+12:00 xinyu liu <xinyuliu...@gmail.com>: > Hi, All, > > There have been quite a lot of new features added to master since 0.10 > release to warrant a new major release. At LinkedIn, we've done functional > and performance testing against master in the past weeks, and deployed jobs > with the latest build in production. We will continue to test for stability > in the next few weeks. > > Here are the JIRAs of main features that will be included in this release > (sorted in chronological order): > > SAMZA-876: Add AvroDataFileHdfsWriter > SAMZA-849: Split-deployment of samza framework > SAMZA-905: Host Affinity - Continuous offset > SAMZA-906: Host Affinity - Minimize task reassignment when container count > changes > SAMZA-924: Disk Quotas: Add disk space monitoring > SAMZA-956: Disk Quotas: Add throttler and disk quota enforcement > SAMZA-680: Inverting JobCoordinator and SamzaAppMaster logic > SAMZA-863: Multithreading support in Samza > > And the JIRAs that I think we should try and get done before 0.11.0 is > released: > > SAMZA-980: Automatically restart job containers on change in upstream > partitioning > SAMZA-988: Update failure testing job configs with job coordinator > properties > SAMZA-997: Add documentation about disk space monitoring > SAMZA-977: User doc for samza multithreading > SAMZA-998: Documentation updates for refactored JC > SAMZA-1000: Hello-samza latest is broken after Samza 10.1 release > > > Here's what I purpose: > > 1. Cut an 0.11.0 release branch. > 2. Work on getting as many of the pending JIRAs done as possible. > 2. Target a release vote on the week of Sep 5. > > Thoughts? > > Xinyu >
