Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/2169
+1
We've been setting `hadoop.version` as 2.6.1 for a long period so if it's
an workaround for lower version, we could remove it. But it would be better to
wait for @revans2 to review this as
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/2163
@vyan Please squash commits into one after addressing my comment. Thanks in
advance.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as wel
Github user HeartSaVioR commented on a diff in the pull request:
https://github.com/apache/storm/pull/2163#discussion_r123164663
--- Diff:
external/storm-redis/src/main/java/org/apache/storm/redis/common/config/JedisClusterConfig.java
---
@@ -45,6 +45,26 @@
* @param node
GitHub user liu-zhaokun opened a pull request:
https://github.com/apache/storm/pull/2170
[STORM-2564] We should provide a template for storm-cluster-auth.yaml
[https://issues.apache.org/jira/browse/STORM-2564](https://issues.apache.org/jira/browse/STORM-2564)
As the configuratio
GitHub user arunmahadevan opened a pull request:
https://github.com/apache/storm/pull/2169
[STORM-2563] Remove the workaround to handle missing
UGI.loginUserFromSubject
https://github.com/apache/storm/blob/master/storm-client/src/jvm/org/apache/storm/security/auth/kerberos/Aut
Github user arunmahadevan commented on the issue:
https://github.com/apache/storm/pull/2168
+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 wishes so, or if the fe
Github user arunmahadevan commented on the issue:
https://github.com/apache/storm/pull/2167
+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 wishes so, or if the fe
>From the perspective of a user who wraps a config driven product around
Storm, the setup of the KafkaSpout, and its configuration, has been a
moving target that is hard to track. In addition, the lack of supporting
usage examples across the README vs examples/ has also made it difficult.
My opini
Github user srishtyagrawal commented on the issue:
https://github.com/apache/storm/pull/2109
@HeartSaVioR thanks for the approval. I have rebased the changes on top of
the latest master branch. Can you please merge this PR?
---
If your project is set up for it, you can reply to this
GitHub user priyank5485 opened a pull request:
https://github.com/apache/storm/pull/2168
STORM-2562: Use stronger key size than default for blow fish key geneâ¦
â¦rator and get rid of stack trace
You can merge this pull request into a Git repository by running:
$ git pull htt
GitHub user priyank5485 opened a pull request:
https://github.com/apache/storm/pull/2167
STORM-2562: Use stronger key size than default for blow fish key geneâ¦
â¦rator and get rid of stack trace
You can merge this pull request into a Git repository by running:
$ git pull htt
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/2164
---
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 enab
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/2162
---
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 enab
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/2164
OK. +1 from me.
---
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, o
14 matches
Mail list logo
