I’m working on a blog post for the 0.10.0 release and plan on highlighting the
main new features. There are a lot and I want to make sure I mention them.
Below is what I have off the top of my head (in no particular order aside from
the fist):
* Security (the big one)
* Support for future r
What do you mean by not backwards compatible? From the API perspective it
should be binary compatible, and should be able to run old topologies without a
recompile (assuming no dependencies from storm were used, and I believe at
least one config was removed, but you would have to check). When r
I'm thinking also about external components. I'm not in front of source right
now, but I think we changed the kafka config in a non backward compatible way.
We're probably okay with a statement about recompiling. And, yes, older
components such as storm-kafka should continue to work without repa
Ya the reason I have been thinking about it is because we have been trough it
with our customers for security already, and we have are preparing for
upmerging to 0.10.0 and we need to tell our customers what to do.
- Bobby
On Monday, June 8, 2015 5:15 PM, P. Taylor Goetz wrote:
I
Here’s the latest working draft of the blog post, which I hope to post on
Monday following the release.
(note that I haven’t finished the shaded dependency table)
Any feedback is welcome.
-Taylor
---
layout: post
title: Storm 0.10.0-beta Released
author: P. Taylor Goetz
---
Fast on the heals
It looks good to me. There are a few spelling mistakes, that TextMate pointed
out to me, but beyond that it looks fine.
- Bobby
On Friday, June 12, 2015 4:26 PM, P. Taylor Goetz
wrote:
Here’s the latest working draft of the blog post, which I hope to post on
Monday following th
