Announcing the release of Apache Samza 0.9.1
I am very excited to announce that Apache Samza 0.9.1 has been released. It's our second release as an Apache Top-level Project. Samza is a distributed stream processing framework. It uses Apache Kafka for messaging, and Apache Hadoop YARN to provide fault tolerance, processor isolation, security, and resource management. The project entered Apache Incubator in 2013 and was originally created at LinkedIn, where it's in production use, and then graduated from Apache Incubator in Jan, 2015. The project is currently under active development from a diverse group of contributors and committers.
A source download of the 0.9.1 release is available here. The release JARs are also available in Apache's Maven repository. See Samza's download page for details.
As a bug-fix version, in all, 7 JIRAs were resolved in this release. A few highlights:
- Iterator.remove breaks caching layer (SAMZA-658)
- Shutdown hook does not wait for container to finish (SAMZA-616)
- Deserialization error causes SystemConsumers to hang (SAMZA-608)
- Samza auto-creates changelog stream without sufficient partitions when container number > 1 (SAMZA-662)
- Bootstrap hangs (SAMZA-720)
- Fix warnings in samza-api Javadocs (SAMZA-712)
We've also made some community progress during this release:
- Added 1 more companies in the powered by page (State)
- Second Samza meetup
- 927 emails sent to the developer mailing list in past 3 months
- Accepted patches from 16 distinct contributors.
There are a lot exciting features to expect in our future release. Some of them are:
- Samza standalone mode (SAMZA-516)
- Yarn host affinity (SAMZA-617)
- State store debugging tool (SAMZA-598)
- Configure Samza jobs through a stream (SAMZA-348)
0.9.1 release will still support java 1.6 to maintain backward compatibility with 0.9.0. We will require java 1.7+ since 0.10.0 release.
Now is a good time to get involved. You can start by running through the hello-samza tutorial, signing up for the mailing list, and grabbing some newbie JIRAs.
I'd like to close by thanking everyone who's been involved in the project. It's been a great experience to be involved in this community, and I look forward to its continued growth.