[jira] [Created] (STORM-554) the get-task-object function in task.clj,the type of first param topology should be ^StormTopology not ^TopologyContext

2014-11-13 Thread zhangjinlong (JIRA)
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:

[jira] [Assigned] (STORM-554) the get-task-object function in task.clj,the type of first param topology should be ^StormTopology not ^TopologyContext

2014-11-13 Thread zhangjinlong (JIRA)
[ 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

[jira] [Commented] (STORM-554) the get-task-object function in task.clj,the type of first param topology should be ^StormTopology not ^TopologyContext

2014-11-13 Thread zhangjinlong (JIRA)
[ 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

[jira] [Resolved] (STORM-554) the get-task-object function in task.clj,the type of first param topology should be ^StormTopology not ^TopologyContext

2014-11-13 Thread zhangjinlong (JIRA)
[ 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

[jira] [Updated] (STORM-554) the get-task-object function in task.clj,the type of first param topology should be ^StormTopology not ^TopologyContext

2014-11-13 Thread zhangjinlong (JIRA)
[ 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

[jira] [Commented] (STORM-216) Secure Multi-tenant Storm

2014-11-13 Thread ASF GitHub Bot (JIRA)
[ 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] storm pull request: STORM-216: Added Authentication and Authorizat...

2014-11-13 Thread ptgoetz
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.

Re: Enquiry regarding a project on @stormprocessor

2014-11-13 Thread Abhishek Bhattacharjee
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

[jira] [Resolved] (STORM-216) Secure Multi-tenant Storm

2014-11-13 Thread Robert Joseph Evans (JIRA)
[ 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] storm pull request: STORM-216: Added Authentication and Authorizat...

2014-11-13 Thread asfgit
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

[jira] [Commented] (STORM-216) Secure Multi-tenant Storm

2014-11-13 Thread ASF GitHub Bot (JIRA)
[ 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] storm pull request: Storm json response should set charset to UTF-...

2014-11-13 Thread Parth-Brahmbhatt
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

[jira] [Updated] (STORM-555) Storm Json response encoding should be UTF-8

2014-11-13 Thread Parth Brahmbhatt (JIRA)
[ 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] storm pull request: Storm555: Storm json response should set chars...

2014-11-13 Thread harshach
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] storm pull request: Storm555: Storm json response should set chars...

2014-11-13 Thread HeartSaVioR
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