Github user srdo commented on the issue:
https://github.com/apache/storm/pull/2159
As I recall (it's been a while), the eventlogging functionality enabled
with "topology.eventlogger.executors" in storm.yaml will make both spouts and
bolts send whatever they emit to an event logger bolt for logging. Spouts
additionally send the message id
https://github.com/apache/storm/blob/a4afacd9617d620f50cf026fc599821f7ac25c79/storm-client/src/jvm/org/apache/storm/executor/spout/SpoutOutputCollectorImpl.java#L111.
This requires the message id to be serializable, or the spout executor will
start throwing exceptions as soon as the button to enable debug logging is
pressed in Storm UI.
@priyank5485
No, I don't see a reason not to do this.
---
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.
---
