You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@storm.apache.org by "Robert Joseph Evans (JIRA)" <ji...@apache.org> on 2017/09/21 18:01:00 UTC
[jira] [Resolved] (STORM-2748) TickTupleTest is useless
[ https://issues.apache.org/jira/browse/STORM-2748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Joseph Evans resolved STORM-2748.
----------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0
> TickTupleTest is useless
> ------------------------
>
> Key: STORM-2748
> URL: https://issues.apache.org/jira/browse/STORM-2748
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-server
> Affects Versions: 2.0.0
> Reporter: Robert Joseph Evans
> Assignee: Robert Joseph Evans
> Labels: pull-request-available
> Fix For: 2.0.0
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> The test starts up a small topology on a simulated time cluster with TOPOLOGY_TICK_TUPLE_FREQ_SECS set to 1. Then it simulates 2 seconds of cluster time. This is not enough time to even launch the topology. How do I know this? Because the Bolt and Spout in the topology override `writeObject` so the resulting serialized bolt and spout are empty and trying to deserialize them results in an exception.
> Just running a topology that does nothing and never verifies that the ticks showed up is a really horrible test. We should either delete it entirely or actually verify that ticks are showing up once a second. I am leaning towards just removing it totally.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)