Github user srdo commented on the issue:
https://github.com/apache/storm/pull/2117
@erikdw Doesn't seem like anyone else is going to chime in. I can't speak
for most of the Storm components, but I believe at least storm-kafka-client has
a fair number of breaking API changes between 1.x and 2.x. It also seems likely
to me that the Java port work would have broken some APIs. Looking at some
topology code I have lying around, there's a decent number of compile errors
after switching to 2.0.0-SNAPSHOT from 1.1.0
I think if we're going to rename methods it would be good to get them all
out of the way in a single release. That way it isn't going to become a regular
nuisance. We could make sure to get them all fixed now, and then put
deprecations for all of them in 1.x?
I agree that this isn't that important of a change, but my impression is
that people are probably going to need to change their code anyway when
migrating to 2.x, so I don't know that it adds that much of an additional cost.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
