Github user srdo commented on the issue:
https://github.com/apache/storm/pull/2147
@hmcl I think it's fine to fix this if users have a problem that can't be
fixed without a code change, but I'm wondering if having them switch to manual
assignment wouldn't work? I think it would be worth checking before we start
making this type of workaround. As far as I know it should be fairly easy to
try out.
You're very likely right that most people are using the `subscribe` API,
but I'd guess that's because it's the default, rather than through any active
decision on their part. Given the problems using the `subscribe` API
introduces, I'd like to know if anyone has a good use case for it before we
start adding support code into the spout to work around quirks with the way
automatic assignment works.
Just to clarify as well, the manual partition assignment is still dynamic
(in the sense that it'll update to account for new partitions), it's just being
done by the spout code rather than Kafka.
I'll start a thread on this on the dev list.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
