[
https://issues.apache.org/jira/browse/STORM-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352544#comment-14352544
]
ASF GitHub Bot commented on STORM-699:
--
Github user harshach commented on the pull req
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/458#issuecomment-77799714
+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 nathanmarz commented on the pull request:
https://github.com/apache/storm/pull/460#issuecomment-77798677
-1
Agree with Parth. Modifying the generated files is out of the question. The
Thrift compiler should be patched to add those annotations if it doesn't have
an
[
https://issues.apache.org/jira/browse/STORM-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352453#comment-14352453
]
ASF GitHub Bot commented on STORM-446:
--
Github user Parth-Brahmbhatt commented on the
Github user Parth-Brahmbhatt commented on the pull request:
https://github.com/apache/storm/pull/448#issuecomment-77792040
@harshach sorry about that I introduced that failure when I added the rest
support and forgot to run the unit tests after that. I have fixed the failing
tests.
Karl Richter created STORM-700:
--
Summary: Add a hint about auto-generation in java source
Key: STORM-700
URL: https://issues.apache.org/jira/browse/STORM-700
Project: Apache Storm
Issue Type: Im
Github user Parth-Brahmbhatt commented on the pull request:
https://github.com/apache/storm/pull/460#issuecomment-77788298
I don't think we should modify the thrift generated files, any way we could
tell thrift to generate these annotation? If not, can we leave those files as
is given
GitHub user krichter722 opened a pull request:
https://github.com/apache/storm/pull/460
added missing @Override annotations
help to detect inheritance issues when generics are used more intensively
You can merge this pull request into a Git repository by running:
$ git pull htt
GitHub user krichter722 opened a pull request:
https://github.com/apache/storm/pull/459
avoiding rawtypes in IBold.prepare in order to allow usage without @Supp...
...ressWarnings("rawtypes") which can be quite annoying during intensive
usage of storm. Some classes which don't have
[
https://issues.apache.org/jira/browse/STORM-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani resolved STORM-242.
--
Resolution: Fixed
> Rotated metrics.log.* should use ${storm.home} in cluster.xml
[
https://issues.apache.org/jira/browse/STORM-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352365#comment-14352365
]
Sriharsha Chintalapani commented on STORM-242:
--
This is fixed in master closin
[
https://issues.apache.org/jira/browse/STORM-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani resolved STORM-457.
--
Resolution: Cannot Reproduce
> Unable to kill topologies whose name has spaces
>
[
https://issues.apache.org/jira/browse/STORM-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani resolved STORM-400.
--
Resolution: Fixed
> Thrift upgrade to 0.9.1
> ---
>
>
[
https://issues.apache.org/jira/browse/STORM-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani resolved STORM-388.
--
Resolution: Fixed
> make supervisor more resilient to missing .ser files
> --
[
https://issues.apache.org/jira/browse/STORM-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani updated STORM-400:
-
Assignee: Kishor Patil
> Thrift upgrade to 0.9.1
> ---
>
>
[
https://issues.apache.org/jira/browse/STORM-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani resolved STORM-531.
--
Resolution: Fixed
> NoOutputException error when a topology is submitted:
> "jav
[
https://issues.apache.org/jira/browse/STORM-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani reassigned STORM-531:
Assignee: Sriharsha Chintalapani
> NoOutputException error when a topology i
[
https://issues.apache.org/jira/browse/STORM-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352363#comment-14352363
]
Sriharsha Chintalapani commented on STORM-426:
--
Coljure is at 1.6 in master. C
[
https://issues.apache.org/jira/browse/STORM-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani resolved STORM-426.
--
Resolution: Fixed
> Upgrade to Clojure 1.6
> --
>
>
[
https://issues.apache.org/jira/browse/STORM-214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani updated STORM-214:
-
Assignee: Sriharsha Chintalapani
> Windows: storm.cmd does not properly handle mult
[
https://issues.apache.org/jira/browse/STORM-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani updated STORM-591:
-
Assignee: Kai Sasaki
> logback.xml
> ---
>
> Key: STORM-591
[
https://issues.apache.org/jira/browse/STORM-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani closed STORM-661.
Resolution: Duplicate
> java.io.FileNotFoundException: File 'stormconf.ser' does not
[
https://issues.apache.org/jira/browse/STORM-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani resolved STORM-652.
--
Resolution: Fixed
> Use latest junit 4.11
> -
>
>
[
https://issues.apache.org/jira/browse/STORM-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani resolved STORM-686.
--
Resolution: Fixed
> Add worker-launcher to storm-dist
> -
[
https://issues.apache.org/jira/browse/STORM-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani resolved STORM-659.
--
Resolution: Fixed
> Logviewer used with grep param returns all matches on one lin
[
https://issues.apache.org/jira/browse/STORM-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352249#comment-14352249
]
ASF GitHub Bot commented on STORM-446:
--
Github user harshach commented on the pull req
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/448#issuecomment-3604
@Parth-Brahmbhatt Overall code looks good to me. I am trying to run few
tests in secure cluster but during mvn build the following unit test is
failing
[
https://issues.apache.org/jira/browse/STORM-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani resolved STORM-675.
--
Resolution: Fixed
> Allow users to have storm-env.sh under config dir to set cust
[
https://issues.apache.org/jira/browse/STORM-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352224#comment-14352224
]
ASF GitHub Bot commented on STORM-446:
--
Github user Parth-Brahmbhatt commented on a di
Github user Parth-Brahmbhatt commented on a diff in the pull request:
https://github.com/apache/storm/pull/448#discussion_r26008403
--- Diff: STORM-UI-REST-API.md ---
@@ -32,6 +32,11 @@ You can use a tool such as `curl` to talk to the REST
API:
# Note: We assume ui.port is
[
https://issues.apache.org/jira/browse/STORM-653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352174#comment-14352174
]
ASF GitHub Bot commented on STORM-653:
--
Github user asfgit closed the pull request at:
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/413
---
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 enabl
[
https://issues.apache.org/jira/browse/STORM-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352173#comment-14352173
]
ASF GitHub Bot commented on STORM-682:
--
Github user harshach commented on the pull req
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/437#issuecomment-77764874
@nathanmarz we need this PR for 0.9.4 release . Please take a look at the
latest patch.
---
If your project is set up for it, you can reply to this email and have your
r
[
https://issues.apache.org/jira/browse/STORM-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352172#comment-14352172
]
ASF GitHub Bot commented on STORM-659:
--
Github user asfgit closed the pull request at:
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/420
---
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 enabl
[
https://issues.apache.org/jira/browse/STORM-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani updated STORM-693:
-
Assignee: Parth Brahmbhatt
> KafkaBolt exception handling improvement
> ---
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/446
---
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 enabl
[
https://issues.apache.org/jira/browse/STORM-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352163#comment-14352163
]
ASF GitHub Bot commented on STORM-496:
--
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/STORM-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352154#comment-14352154
]
ASF GitHub Bot commented on STORM-659:
--
Github user harshach commented on the pull req
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/420#issuecomment-77763288
+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
[
https://issues.apache.org/jira/browse/STORM-693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352152#comment-14352152
]
ASF GitHub Bot commented on STORM-693:
--
Github user asfgit closed the pull request at:
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/453
---
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 enabl
[
https://issues.apache.org/jira/browse/STORM-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352146#comment-14352146
]
ASF GitHub Bot commented on STORM-446:
--
Github user harshach commented on a diff in th
Github user harshach commented on a diff in the pull request:
https://github.com/apache/storm/pull/448#discussion_r26007092
--- Diff: STORM-UI-REST-API.md ---
@@ -32,6 +32,11 @@ You can use a tool such as `curl` to talk to the REST
API:
# Note: We assume ui.port is configu
[
https://issues.apache.org/jira/browse/STORM-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352145#comment-14352145
]
ASF GitHub Bot commented on STORM-675:
--
Github user asfgit closed the pull request at:
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/434
---
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 enabl
Hello everyone,
I would like to contribute to the project in some way
(coding/documentation).
Could you help me with some guidance on where to begin?
For example I've seen on the website that it's recommended to start with
the "newbie" labelled jira issues.
Thanks in advance,
Dan Huru
48 matches
Mail list logo
