Github user hmcl commented on the issue:
https://github.com/apache/storm/pull/2147
@srdo I agree that this is not the ideal solution, and that's precisely the
reason why the pre-fetch tasks are pluggable. There are better approaches to do
this, but this one fixes some immediate problems for some customers.
The discussion of whether supporting dynamic partition assignment or only
fixed partition should be done in the email list. I think that we should still
support it, at least for 1.x-branch as there are customers using it already. I
would conjecture that way more people are using dynamic vs fixed. For 2.0 is a
matter of deciding what we want to do, and if we end up supporting both, we
should really separate concerns handling fixed and dynamic partition assignment.
---
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.
---
