Github user ohadedel commented on the issue:
https://github.com/apache/storm/pull/1790
Sound reasonable :)
The documentation in storm was a bit misleading, made us think that its
being implemented the same.
"None grouping: This grouping specifies that you don't care how the stream
is grouped. Currently, none groupings are equivalent to shuffle groupings.
Eventually though, Storm will push down bolts with none groupings to execute in
the same thread as the bolt or spout they subscribe from (when possible)."
One last question @HeartSaVioR , we are running on v0.9.3 for the last two
years, and i am working to upgrade us to v1.0.x
There are a few guys at my company that say: maybe we should wait and make
sure the version will be stabler.
This issue with the ShuffleGrouping is pretty small bug but it cause a very
big performance issue and we were surprise to be one of the first to stumble on
it, so at first we thought we did something wrong while installing.
Do you have any better insight to the version? because i really want to
bring all the new features that this version has.
Thanks!
---
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.
---
