Github user Ethanlm commented on the issue:
https://github.com/apache/storm/pull/2242
---
If your project is set up for it, you can reply to this email and have your
reply
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/2242
Actually this issue is the subtask of topology online update, and topology
version is expected to be set automatically to the increasing number.
But I also think this patch doesn't hurt in any
Github user Ethanlm commented on the issue:
https://github.com/apache/storm/pull/2242
Thanks for review @HeartSaVioR
---
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
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/2242
@Ethanlm
Sorry there's merge conflict now. Could you resolve this?
You may want to just regenerate classes from thrift since the conflict
occurs from generated files.
---
If your projec
Github user Ethanlm commented on the issue:
https://github.com/apache/storm/pull/2242
Thanks @HeartSaVioR Regenerated them
---
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
enable
Github user Ethanlm commented on the issue:
https://github.com/apache/storm/pull/2242
storm-cassandra failed. Should be not related to this PR.
---
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
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/2242
+1
---
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 feat
