zhangjinlong created STORM-554:
--
Summary: the get-task-object function in task.clj,the type of
first param topology should be ^StormTopology not ^TopologyContext
Key: STORM-554
URL:
[
https://issues.apache.org/jira/browse/STORM-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjinlong reassigned STORM-554:
--
Assignee: zhangjinlong
the get-task-object function in task.clj,the type of first param
[
https://issues.apache.org/jira/browse/STORM-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14209525#comment-14209525
]
zhangjinlong commented on STORM-554:
(defn- get-task-object [^TopologyContext topology
[
https://issues.apache.org/jira/browse/STORM-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjinlong resolved STORM-554.
Resolution: Fixed
Update get-task-object function, change the type of first param topology
from
[
https://issues.apache.org/jira/browse/STORM-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
zhangjinlong updated STORM-554:
---
Description: the get-task-object function in task.clj,the type of first
param topology should be
[
https://issues.apache.org/jira/browse/STORM-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14210141#comment-14210141
]
ASF GitHub Bot commented on STORM-216:
--
Github user revans2 commented on the pull
Github user ptgoetz commented on the pull request:
https://github.com/apache/storm/pull/121#issuecomment-62946641
@revans2 Yeah, I created that branch earlier today then got distracted by
meetings before I could send out a notification. That branch is currently
identical to master.
Benchmarks from various scenario is very important because high
probabilities of failing tuples is not normal situation.
If it only covers with specific situation, I think it needs to be more
general.
I hope to see your future plan about this.
I think we can do this. We can do our
[
https://issues.apache.org/jira/browse/STORM-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans resolved STORM-216.
---
Resolution: Fixed
Fix Version/s: 0.10.0
This was merged into master.
Secure
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/121
---
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
[
https://issues.apache.org/jira/browse/STORM-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14211294#comment-14211294
]
ASF GitHub Bot commented on STORM-216:
--
Github user asfgit closed the pull request at:
GitHub user Parth-Brahmbhatt opened a pull request:
https://github.com/apache/storm/pull/313
Storm json response should set charset to UTF-8.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Parth-Brahmbhatt/incubator-storm
[
https://issues.apache.org/jira/browse/STORM-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Parth Brahmbhatt updated STORM-555:
---
Description:
Currently the storm Rest API responses has charset=iso-8859-1 set by ring/jetty
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/313#issuecomment-62990323
+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 and
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/313#issuecomment-62992440
Looks good!
---
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
15 matches
Mail list logo