GitHub user SeanTAllen opened a pull request:
https://github.com/apache/storm/pull/309
STORM-549: "topology.enable.message.timeouts" does nothing
The ability to turn off message timeouts doesn't work.
The value is a true/false value that is represented as
a Java Boolean. The check for the truthiness used the
clojure not function. The idea was, turn off message
timeouts if "topology.enable.message.timeouts" is not true.
Unfortunately this won't worth with clojure's definition of
truthiness as:
(not (Boolean. false))
evaluates to true.
This commit updates the logic to compare the Java Boolean
"topology.enable.message.timeouts" to false using the
= function which will work.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/SeanTAllen/storm master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/309.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #309
----
commit 0505d47471170861ad303dc530a8d8de4e730c10
Author: Sean T Allen <[email protected]>
Date: 2014-11-08T14:41:29Z
STORM-549: "topology.enable.message.timeouts" does nothing
The ability to turn off message timeouts doesn't work.
The value is a true/false value that is represented as
a Java Boolean. The check for the truthiness used the
clojure not function. The idea was, turn off message
timeouts if "topology.enable.message.timeouts" is not true.
Unfortunately this won't worth with clojure's definition of
truthiness as:
(not (Boolean. false))
evaluates to true.
This commit updates the logic to compare the Java Boolean
"topology.enable.message.timeouts" to false using the
= function which will work.
----
---
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.
---
