Github user nielsbasjes commented on the pull request:
https://github.com/apache/storm/pull/275#issuecomment-63355100
I'll have a look into why these tests failed.
Regarding the 'why':
A Tick is a message between the Storm framework and a bolt that runs within
the framework. Kafka bolt should handle the tick any way suitable, but most
importantly is must NOT persist the tick into Kafka.
I ran into the scenario that a non-Storm consumer of this Kafka topic gave
errors because it got a message (= a Tick) that did not adhere to the agreed
interface (i.e. I got deserialization exceptions).
So that's why.
---
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.
---
