[
https://issues.apache.org/jira/browse/STORM-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans resolved STORM-623.
---
Resolution: Fixed
Fix Version/s: 0.10.0
Thanks [~lewuathe],
I merged this into
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/387#issuecomment-72542849
@ptgoetz makes sense. STORM-631 aiming to be a umbrella jira. Creating
another jira is fine too.
---
If your project is set up for it, you can reply to this email and
Github user wurstmeister commented on the pull request:
https://github.com/apache/storm/pull/406#issuecomment-72532975
Hi,
Thanks for pointing out your PR. This looks like it is fairly similar to
https://github.com/apache/storm/pull/254, which has been merged recently.
In the past, the storm project used log4j version 1.x as its logging
framework. Around the time of 0.9.0, before moving to Apache, the project
moved to using logback for two reasons:
1) logback supported rolling log files, which was critical for managing disk
space usage.
2) logback supported
Github user wurstmeister commented on the pull request:
https://github.com/apache/storm/pull/387#issuecomment-72537785
sounds 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
[
https://issues.apache.org/jira/browse/STORM-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani updated STORM-651:
-
Summary: improvements to storm.cmd (was: Add jdk and jres bin and libs
dirs to
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/389#issuecomment-72539951
There is a lot of code in here that I don't understand how it relates to
STORM-528. Setting the code dir, is not really something that I think we want
to expose, except
[
https://issues.apache.org/jira/browse/STORM-528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14301949#comment-14301949
]
ASF GitHub Bot commented on STORM-528:
--
Github user revans2 commented on the pull
[
https://issues.apache.org/jira/browse/STORM-650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14302058#comment-14302058
]
ASF GitHub Bot commented on STORM-650:
--
Github user ptgoetz commented on the pull
Sriharsha Chintalapani created STORM-651:
Summary: Add jdk and jres bin and libs dirs to lib path in
storm.cmd
Key: STORM-651
URL: https://issues.apache.org/jira/browse/STORM-651
Project:
Sriharsha Chintalapani created STORM-649:
Summary: Storm HDFS test topologies should write to /tmp dir
Key: STORM-649
URL: https://issues.apache.org/jira/browse/STORM-649
Project: Apache Storm
Github user revans2 commented on the pull request:
https://github.com/apache/storm/pull/288#issuecomment-72536306
@BuDongDong I merged this in, but because your repo was deleted the pull
request is not automatically recognizing that it was pulled in. Could you
check master and close
Github user Parth-Brahmbhatt commented on the pull request:
https://github.com/apache/storm/pull/387#issuecomment-72536213
@ptgoetz Makes sense.
---
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
P. Taylor Goetz created STORM-650:
-
Summary: Storm-Kafka Refactoring and Improvements
Key: STORM-650
URL: https://issues.apache.org/jira/browse/STORM-650
Project: Apache Storm
Issue Type:
Github user ptgoetz commented on the pull request:
https://github.com/apache/storm/pull/387#issuecomment-72551762
STORM-650 created. Let's try to focus discussion/efforts there.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
GitHub user kishorvpatil opened a pull request:
https://github.com/apache/storm/pull/410
[STORM-400] Thrift upgrade to thrift-0.9.2
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kishorvpatil/incubator-storm thrift092
[
https://issues.apache.org/jira/browse/STORM-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14302535#comment-14302535
]
ASF GitHub Bot commented on STORM-400:
--
GitHub user kishorvpatil opened a pull
[
https://issues.apache.org/jira/browse/STORM-639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14302085#comment-14302085
]
ASF GitHub Bot commented on STORM-639:
--
Github user d2r commented on the pull request:
GitHub user harshach opened a pull request:
https://github.com/apache/storm/pull/408
STORM-648. storm examples BasicDRPCTopology fails without running.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/harshach/incubator-storm
[
https://issues.apache.org/jira/browse/STORM-641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14302573#comment-14302573
]
ASF GitHub Bot commented on STORM-641:
--
GitHub user harshach opened a pull request:
GitHub user harshach opened a pull request:
https://github.com/apache/storm/pull/412
STORM-640. Storm UI vulnerable to poodle attack.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/harshach/incubator-storm STORM-640
[
https://issues.apache.org/jira/browse/STORM-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14302590#comment-14302590
]
ASF GitHub Bot commented on STORM-640:
--
GitHub user harshach opened a pull request:
[
https://issues.apache.org/jira/browse/STORM-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14302069#comment-14302069
]
Sriharsha Chintalapani commented on STORM-651:
--
1) Add jdk and jres bin and
[
https://issues.apache.org/jira/browse/STORM-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sriharsha Chintalapani updated STORM-651:
-
Priority: Minor (was: Trivial)
improvements to storm.cmd
GitHub user harshach opened a pull request:
https://github.com/apache/storm/pull/409
STORM-652. Use latest junit 4.11 .
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/harshach/incubator-storm STORM-652
Alternatively you can
Github user d2r commented on the pull request:
https://github.com/apache/storm/pull/403#issuecomment-72554412
Update documents to install storm-maven-plugin before compiling
storm-core project.
Yeah... I was afraid of that. It is a binary dependency, and maven does
not
[
https://issues.apache.org/jira/browse/STORM-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14302517#comment-14302517
]
ASF GitHub Bot commented on STORM-652:
--
GitHub user harshach opened a pull request:
[
https://issues.apache.org/jira/browse/STORM-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14302499#comment-14302499
]
ASF GitHub Bot commented on STORM-648:
--
GitHub user harshach opened a pull request:
GitHub user harshach opened a pull request:
https://github.com/apache/storm/pull/411
STORM-641. Add total number of topologies to api/v1/cluster/summary.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/harshach/incubator-storm
GitHub user ogorun opened a pull request:
https://github.com/apache/storm/pull/406
Kafka spout failure config
This pull request offers plugable MessageFailureHandler for failed message.
Solution structure.
PartitionManger uses instance of class that implements
[
https://issues.apache.org/jira/browse/STORM-631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14301350#comment-14301350
]
ASF GitHub Bot commented on STORM-631:
--
Github user harshach commented on the pull
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/406#issuecomment-72469942
@ogorun There is work in progress to refactor kafka code at STORM-631. Can
you please add your requirements/issue there so that we can fix it as part of
STORM-631.
[
https://issues.apache.org/jira/browse/STORM-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14301357#comment-14301357
]
ASF GitHub Bot commented on STORM-637:
--
Github user revans2 commented on the pull
[
https://issues.apache.org/jira/browse/STORM-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans resolved STORM-527.
---
Resolution: Fixed
Fix Version/s: (was: 0.9.3)
0.10.0
[
https://issues.apache.org/jira/browse/STORM-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14301858#comment-14301858
]
ASF GitHub Bot commented on STORM-623:
--
Github user asfgit closed the pull request at:
[
https://issues.apache.org/jira/browse/STORM-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14301852#comment-14301852
]
ASF GitHub Bot commented on STORM-623:
--
Github user revans2 commented on the pull
[
https://issues.apache.org/jira/browse/STORM-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14301491#comment-14301491
]
Parth Brahmbhatt commented on STORM-590:
Thanks for assigning it to me, I have
Github user ogorun commented on the pull request:
https://github.com/apache/storm/pull/387#issuecomment-72505185
Hi @Parth-Brahmbhatt ,
Thank you for pointing me to this pull request. I see that my pull request
https://github.com/apache/storm/pull/406 shares part of ideas
GitHub user wurstmeister opened a pull request:
https://github.com/apache/storm/pull/407
Storm 590: added Kafka API based partition reader
Following the discussion in https://github.com/apache/storm/pull/387 I've
prepared an alternative implementation that is backwards compatible
Github user wurstmeister commented on the pull request:
https://github.com/apache/storm/pull/387#issuecomment-72496938
Hi,
i've created a backwards compatible alternative focused on using the Kafka
API for reading partition information in
Github user Parth-Brahmbhatt commented on the pull request:
https://github.com/apache/storm/pull/331#issuecomment-72499073
+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
Github user harshach commented on the pull request:
https://github.com/apache/storm/pull/354#issuecomment-72519250
@Parth-Brahmbhatt I apologize for not getting to this earlier. I took a
first-pass at the code and tested it in cluster. Here are my thoughts and
nitpicks :)
1.
[
https://issues.apache.org/jira/browse/STORM-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kai Sasaki updated STORM-590:
-
Assignee: Parth Brahmbhatt (was: Kai Sasaki)
KafkaSpout should use kafka consumer api
[
https://issues.apache.org/jira/browse/STORM-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14301025#comment-14301025
]
Kai Sasaki commented on STORM-590:
--
[~parth.brahmbhatt] Of couse, it's ok to assign this
44 matches
Mail list logo