For all of these we should be able to support a rolling upgrade from 1.x with
some caveats.
1) There are a few possibilities on how to make this happen, but none of them
are ideal. If you feel strongly about a rolling upgrade I might skip this.
2) would work for all workers that do not access
My only concern here is the rolling upgrade of storm cluster. We supported
the rolling upgrade going to 0.10 and broke it because of storm 1.x
release. Users are not inclined to upgrade to a new release if it's not
rolling upgradable. In this case, it looks like we are going to break this.
Correct
Made a mistake and put something on private that never should have been there.
Here is the discussion in full so far.
In response to Jungtake removing the nocamel option will change set_bar/get_bar
in the generated thrift code to setBar/getBar. So any thrift object that
clients interact with
