GitHub user onlychoice opened a pull request:
https://github.com/apache/storm/pull/398
Fix spout close: close spout when emitter closed
Close the spout when the emitter of TridentSpout closed.
You can merge this pull request into a Git repository by running:
$ git pull https://
GitHub user harisekhon opened a pull request:
https://github.com/apache/storm/pull/397
fixed daemon typo
fixed typo on security page
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/harisekhon/storm security_typo_fixes
Alternative
[
https://issues.apache.org/jira/browse/STORM-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14294134#comment-14294134
]
ASF GitHub Bot commented on STORM-570:
--
Github user kishorvpatil commented on the pull
[
https://issues.apache.org/jira/browse/STORM-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14294135#comment-14294135
]
ASF GitHub Bot commented on STORM-570:
--
Github user kishorvpatil commented on the pull
Github user kishorvpatil commented on the pull request:
https://github.com/apache/storm/pull/328#issuecomment-71722168
@revans2 could you please upmerge the change again?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user kishorvpatil commented on the pull request:
https://github.com/apache/storm/pull/328#issuecomment-71722015
+1
---
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
[
https://issues.apache.org/jira/browse/STORM-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14294071#comment-14294071
]
ASF GitHub Bot commented on STORM-636:
--
Github user d2r commented on the pull request:
Github user d2r commented on the pull request:
https://github.com/apache/storm/pull/392#issuecomment-71714975
> Not to derail the discussion but personally, I would much rather not
store errors in zk at all if its just for rendering the errors in UI. If the
spouts/bolts could just st
[
https://issues.apache.org/jira/browse/STORM-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14293979#comment-14293979
]
ASF GitHub Bot commented on STORM-636:
--
Github user Parth-Brahmbhatt commented on the
Github user Parth-Brahmbhatt commented on the pull request:
https://github.com/apache/storm/pull/392#issuecomment-71706395
I did not know we only stored 10 errors, makes sense to not go with
pagination if its hardcoded to 10. I will take a look at the complete PR today.
Not to
[
https://issues.apache.org/jira/browse/STORM-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14293889#comment-14293889
]
ASF GitHub Bot commented on STORM-636:
--
Github user d2r commented on a diff in the pul
Github user d2r commented on a diff in the pull request:
https://github.com/apache/storm/pull/392#discussion_r23628156
--- Diff: storm-core/src/storm.thrift ---
@@ -243,6 +243,16 @@ struct SubmitOptions {
2: optional Credentials creds;
}
+enum NumErrorsChoice {
[
https://issues.apache.org/jira/browse/STORM-636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14293882#comment-14293882
]
ASF GitHub Bot commented on STORM-636:
--
Github user d2r commented on a diff in the pul
Github user d2r commented on a diff in the pull request:
https://github.com/apache/storm/pull/392#discussion_r23627700
--- Diff: storm-core/src/storm.thrift ---
@@ -243,6 +243,16 @@ struct SubmitOptions {
2: optional Credentials creds;
}
+enum NumErrorsChoice {
[
https://issues.apache.org/jira/browse/STORM-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Derek Dagit resolved STORM-525.
---
Resolution: Fixed
Fix Version/s: 0.10.0
Seems this was merged in.
> UI Component Page Executor
Github user caofangkun commented on the pull request:
https://github.com/apache/storm/pull/396#issuecomment-71607591
Pay Attention: conflicts with https://github.com/apache/storm/pull/296
---
If your project is set up for it, you can reply to this email and have your
reply appear on
[
https://issues.apache.org/jira/browse/STORM-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14293172#comment-14293172
]
ASF GitHub Bot commented on STORM-638:
--
Github user caofangkun commented on the pull r
[
https://issues.apache.org/jira/browse/STORM-638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14293167#comment-14293167
]
ASF GitHub Bot commented on STORM-638:
--
GitHub user caofangkun opened a pull request:
GitHub user caofangkun opened a pull request:
https://github.com/apache/storm/pull/396
STORM-638:UI should show up process-id of the Worker to which an Executor
is assigned
