[
https://issues.apache.org/jira/browse/STORM-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14214986#comment-14214986
]
ASF GitHub Bot commented on STORM-512:
--------------------------------------
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.
> KafkaBolt doesn't handle ticks properly
> ---------------------------------------
>
> Key: STORM-512
> URL: https://issues.apache.org/jira/browse/STORM-512
> Project: Apache Storm
> Issue Type: Bug
> Reporter: Niels Basjes
>
> I found that when using the KafkaBolt the tick tuples are not handled
> properly. They should be ignored and the reality is that they are not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
