[
https://issues.apache.org/jira/browse/STORM-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401509#comment-15401509
]
ASF GitHub Bot commented on STORM-1277:
---------------------------------------
Github user unsleepy22 commented on a diff in the pull request:
https://github.com/apache/storm/pull/1445#discussion_r72922608
--- Diff:
storm-core/test/clj/integration/org/apache/storm/integration_test.clj ---
@@ -403,17 +403,18 @@
(def bolt-prepared? (atom false))
(defbolt prepare-tracked-bolt [] {:prepare true}
[conf context collector]
- (reset! bolt-prepared? true)
(bolt
(execute [tuple]
+ (reset! bolt-prepared? true)
--- End diff --
The basic idea was that, in the original code, `spout-opened?` or
`bolt-prepared?` are set to true in executor initialization phase, while after
porting to java, this behavior is deferred to `execute/nextTuple`.
> port backtype.storm.daemon.executor to java
> -------------------------------------------
>
> Key: STORM-1277
> URL: https://issues.apache.org/jira/browse/STORM-1277
> Project: Apache Storm
> Issue Type: New Feature
> Components: storm-core
> Reporter: Robert Joseph Evans
> Assignee: Cody
> Labels: java-migration, jstorm-merger
>
> https://github.com/apache/storm/tree/jstorm-import/jstorm-core/src/main/java/com/alibaba/jstorm/task
> kind of. Tasks and executors are combined in jstorm.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)