Github user carl34 commented on the issue:
https://github.com/apache/storm/pull/2126
Thanks for the additional context. Our primary objective is to find a way
to update our legacy topologies which use storm-kafka, but it looks like the
clientId member is final in 1.1.0, correct?
https://github.com/apache/storm/blob/a4afacd9617d620f50cf026fc599821f7ac25c79/external/storm-kafka/src/jvm/org/apache/storm/kafka/KafkaConfig.java#L32
We were initially just going to submit a PR for storm-kafka, but we're
hoping to make it clear to new topology creators that client.id is available
because we feel that it is valuable. If the builder pattern is going to be
removed, would it be a big deal to add this change in the mean-time?
---
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.
---
