Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1853
@revans2 I think the direction of STORM-2216 is right, and we just found a
spot which is not trivial to fix to the right way.
---
If your project is set up for it, you can reply to this email an
Github user revans2 commented on the issue:
https://github.com/apache/storm/pull/1853
I am also OK with reverting STORM-2216 if it is causing a lot of issues.
---
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 projec
Github user revans2 commented on the issue:
https://github.com/apache/storm/pull/1853
+1 seems fine to me
---
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, o
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1853
@revans2 Could you please take a look?
---
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
e
Github user hmcl commented on the issue:
https://github.com/apache/storm/pull/1853
+1
@HeartSaVioR [STORM-2265](https://github.com/apache/storm/pull/1844) is a
duplicate of this that I found independently. We can go ahead and merge this
(revert) fix. We can keep STORM-2265 open to
