[
https://issues.apache.org/jira/browse/STORM-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347698#comment-15347698
]
ASF GitHub Bot commented on STORM-1925:
---
Github user asfgit closed the pull request at:
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/1514
---
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
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1436
I'm not clearly saying that it is, but hadoop-auth is added at pom.xml now
and it also refers to same version so version of hadoop-auth also should be
changed when users want to exclude and
Github user mazhechao commented on the issue:
https://github.com/apache/storm/pull/1436
@HeartSaVioR Is hadoop-auth necessary?
---
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
[
https://issues.apache.org/jira/browse/STORM-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347589#comment-15347589
]
ASF GitHub Bot commented on STORM-1929:
---
Github user darionyaphet commented on a diff in the pull
Github user darionyaphet commented on a diff in the pull request:
https://github.com/apache/storm/pull/1515#discussion_r68347350
--- Diff: storm-core/src/jvm/org/apache/storm/topology/TopologyBuilder.java
---
@@ -113,6 +113,15 @@ public StormTopology createTopology() {
Github user hmcl commented on the issue:
https://github.com/apache/storm/pull/1474
@nabhanelrahman your patch enlightened that it would be better to add the
`emit` and `getOutputFields` methods to `KafkaSpoutStream`. Furthermore, there
were a couple of design decisions that would be
[
https://issues.apache.org/jira/browse/STORM-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347533#comment-15347533
]
ASF GitHub Bot commented on STORM-1930:
---
Github user hmcl commented on the issue:
Github user hmcl commented on the issue:
https://github.com/apache/storm/pull/1516
@harshach Should this patch be merged onto 1.x-branch as well. Thanks.
---
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
[
https://issues.apache.org/jira/browse/STORM-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347532#comment-15347532
]
ASF GitHub Bot commented on STORM-1930:
---
GitHub user hmcl opened a pull request:
GitHub user hmcl opened a pull request:
https://github.com/apache/storm/pull/1516
STORM-1930: Kafka New Client API - Support for Topic Wildcards
- Interfaces for TuplesBuilder and KafkaSpoutStreams and implementations
for named topics and wildcards
- Test topologies for named
[
https://issues.apache.org/jira/browse/STORM-1930?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hugo Louro updated STORM-1930:
--
Summary: Kafka New Client API - Support for Topic Wildcards (was: Kafka
New Client API Support for
Hugo Louro created STORM-1930:
-
Summary: Kafka New Client API Support for Topic Wildcards
Key: STORM-1930
URL: https://issues.apache.org/jira/browse/STORM-1930
Project: Apache Storm
Issue Type:
[
https://issues.apache.org/jira/browse/STORM-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347496#comment-15347496
]
ASF GitHub Bot commented on STORM-1885:
---
Github user HeartSaVioR commented on the issue:
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1468
We may have to modify lots of part of script since...
- We don't have develop branch so all about develop branch should be
modified. Spark merge script also doesn't have handling with
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1512
+1 once my comments are addressed.
---
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 HeartSaVioR commented on a diff in the pull request:
https://github.com/apache/storm/pull/1512#discussion_r68336175
--- Diff:
external/storm-hdfs/src/test/java/org/apache/storm/hdfs/trident/TridentSequenceTopology.java
---
@@ -73,14 +75,20 @@ public static
Github user HeartSaVioR commented on a diff in the pull request:
https://github.com/apache/storm/pull/1512#discussion_r68336156
--- Diff:
external/storm-hdfs/src/test/java/org/apache/storm/hdfs/trident/TridentFileTopology.java
---
@@ -75,14 +78,20 @@ public static StormTopology
[
https://issues.apache.org/jira/browse/STORM-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15347442#comment-15347442
]
ASF GitHub Bot commented on STORM-1925:
---
Github user harshach commented on the issue:
Github user harshach commented on the issue:
https://github.com/apache/storm/pull/1513
+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
Github user revans2 commented on a diff in the pull request:
https://github.com/apache/storm/pull/1515#discussion_r68280266
--- Diff: storm-core/src/jvm/org/apache/storm/topology/TopologyBuilder.java
---
@@ -339,8 +353,13 @@ public SpoutDeclarer setSpout(String id, IRichSpout
[
https://issues.apache.org/jira/browse/STORM-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346843#comment-15346843
]
ASF GitHub Bot commented on STORM-1929:
---
Github user revans2 commented on a diff in the pull
[
https://issues.apache.org/jira/browse/STORM-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346842#comment-15346842
]
ASF GitHub Bot commented on STORM-1929:
---
Github user revans2 commented on a diff in the pull
Github user revans2 commented on a diff in the pull request:
https://github.com/apache/storm/pull/1515#discussion_r68280207
--- Diff: storm-core/src/jvm/org/apache/storm/topology/TopologyBuilder.java
---
@@ -179,8 +188,13 @@ public BoltDeclarer setBolt(String id, IRichBolt bolt)
[
https://issues.apache.org/jira/browse/STORM-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346841#comment-15346841
]
ASF GitHub Bot commented on STORM-1929:
---
Github user revans2 commented on a diff in the pull
Github user revans2 commented on a diff in the pull request:
https://github.com/apache/storm/pull/1515#discussion_r68279943
--- Diff: storm-core/src/jvm/org/apache/storm/topology/TopologyBuilder.java
---
@@ -113,6 +113,15 @@ public StormTopology createTopology() {
[
https://issues.apache.org/jira/browse/STORM-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346672#comment-15346672
]
ASF GitHub Bot commented on STORM-1886:
---
Github user kosii commented on a diff in the pull request:
[
https://issues.apache.org/jira/browse/STORM-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346673#comment-15346673
]
ASF GitHub Bot commented on STORM-1886:
---
Github user kosii commented on a diff in the pull request:
Github user kosii commented on a diff in the pull request:
https://github.com/apache/storm/pull/1470#discussion_r68263894
--- Diff:
external/storm-redis/src/main/java/org/apache/storm/redis/state/RedisKeyValueState.java
---
@@ -203,12 +237,14 @@ public void commit() {
Github user kosii commented on a diff in the pull request:
https://github.com/apache/storm/pull/1470#discussion_r68263881
--- Diff:
external/storm-redis/src/main/java/org/apache/storm/redis/state/RedisKeyValueState.java
---
@@ -184,15 +216,17 @@ public void commit(long txid) {
[
https://issues.apache.org/jira/browse/STORM-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346660#comment-15346660
]
ASF GitHub Bot commented on STORM-1929:
---
GitHub user darionyaphet opened a pull request:
GitHub user darionyaphet opened a pull request:
https://github.com/apache/storm/pull/1515
[STORM-1929] Check when create topology
[STORM-1929](https://issues.apache.org/jira/browse/STORM-1929)
Add some check when create topology :
1. Spout and Bolt id shouldn't
[
https://issues.apache.org/jira/browse/STORM-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346658#comment-15346658
]
ASF GitHub Bot commented on STORM-1886:
---
Github user kosii commented on a diff in the pull request:
[
https://issues.apache.org/jira/browse/STORM-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346653#comment-15346653
]
ASF GitHub Bot commented on STORM-1886:
---
Github user kosii commented on a diff in the pull request:
Github user kosii commented on a diff in the pull request:
https://github.com/apache/storm/pull/1470#discussion_r68261133
--- Diff:
external/storm-redis/src/main/java/org/apache/storm/redis/state/RedisKeyValueState.java
---
@@ -77,7 +81,8 @@ public RedisKeyValueState(String
[
https://issues.apache.org/jira/browse/STORM-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346650#comment-15346650
]
ASF GitHub Bot commented on STORM-1886:
---
Github user kosii commented on a diff in the pull request:
Github user kosii commented on a diff in the pull request:
https://github.com/apache/storm/pull/1470#discussion_r68260812
--- Diff: storm-core/src/jvm/org/apache/storm/state/KeyValueState.java ---
@@ -45,4 +45,11 @@
* @return the value or defaultValue if no mapping is
[
https://issues.apache.org/jira/browse/STORM-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346635#comment-15346635
]
ASF GitHub Bot commented on STORM-1886:
---
Github user kosii commented on a diff in the pull request:
darion yaphet created STORM-1929:
Summary: Check when create topology
Key: STORM-1929
URL: https://issues.apache.org/jira/browse/STORM-1929
Project: Apache Storm
Issue Type: Improvement
Github user kosii commented on a diff in the pull request:
https://github.com/apache/storm/pull/1470#discussion_r68260007
--- Diff:
external/storm-redis/src/main/java/org/apache/storm/redis/state/RedisKeyValueState.java
---
@@ -163,15 +190,20 @@ public void prepareCommit(long
Github user harshach commented on the issue:
https://github.com/apache/storm/pull/1512
+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
[
https://issues.apache.org/jira/browse/STORM-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346596#comment-15346596
]
ASF GitHub Bot commented on STORM-1925:
---
Github user harshach commented on the issue:
Github user harshach commented on the issue:
https://github.com/apache/storm/pull/1514
+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
The plan is to have the clojure API moved to the storm-clojure package and
storm-core will no longer depend on clojure.
- Bobby
On Thursday, June 23, 2016 10:02 AM, Junguk Cho wrote:
Hi,
Just to be clear, since it is in the ongoing process to replace clojure
Hi,
Just to be clear, since it is in the ongoing process to replace clojure
codes with java codes, I still can see storm-core/clj/ directory in this
git (https://github.com/apache/storm).
However, when you release storm 2.0 stable version, files in
storm-core/clj/ will be removed.
Is it
[
https://issues.apache.org/jira/browse/STORM-1770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346553#comment-15346553
]
darion yaphet commented on STORM-1770:
--
HI [~abhishek.agarwal] I found a lot Spout (not only
[
https://issues.apache.org/jira/browse/STORM-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346550#comment-15346550
]
Jungtaek Lim commented on STORM-1928:
-
ShellSpout should be changed to alike ShellBolt, I mean having
Jungtaek Lim created STORM-1928:
---
Summary: ShellSpout should send heartbeat tuple while nextTuple()
is not called
Key: STORM-1928
URL: https://issues.apache.org/jira/browse/STORM-1928
Project: Apache
Not that I know of, but better dev tool integration would be a great thing to
have
On Wednesday, June 22, 2016 6:22 PM, Arjun Rao
wrote:
This might be a question answered before, but is there a way (or maybe an open
ticket) to see the Storm UI while running
There is only one thread associated with an input queue and that is the one the
executor runs on. The output queue has a separate thread that all it does is
pop messages off of the output queue and routes them to where they need to be.
In my experience this runs fairly infrequently. I would
[
https://issues.apache.org/jira/browse/STORM-1926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
darion yaphet closed STORM-1926.
Resolution: Won't Fix
> Upgrade Jetty and Ring
> --
>
> Key:
darion yaphet created STORM-1927:
Summary: Upgrade Jetty and Ring
Key: STORM-1927
URL: https://issues.apache.org/jira/browse/STORM-1927
Project: Apache Storm
Issue Type: Improvement
Hi Jacob,
Supervisor node is running, however, it still could not display topology
summary, number of tasks and executors are not displayed.
Is it required to write any code in order for submitted topology to appear in
storm UI?
Thank you--Regards
WA
From: Jacob Johansen
Hi all,
I have submitted ExclamationTopology into single-node cluster Storm 1.0.1, as
following: storm jar target/storm-starter-*.jar
org.apache.storm.starter.ExclamationTopology
I have three basic questions:1- In sotrm UI, http://localhost:8080/index.html ,
the running topology and the number
darion yaphet created STORM-1926:
Summary: Upgrade Jetty and Ring
Key: STORM-1926
URL: https://issues.apache.org/jira/browse/STORM-1926
Project: Apache Storm
Issue Type: Bug
[
https://issues.apache.org/jira/browse/STORM-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346092#comment-15346092
]
ASF GitHub Bot commented on STORM-1925:
---
Github user HeartSaVioR commented on the issue:
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1513
Confirmed that before patch Nimbus has crashed in kerberized environment,
and this patch fixes that issue.
---
If your project is set up for it, you can reply to this email and have your
reply
[
https://issues.apache.org/jira/browse/STORM-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346079#comment-15346079
]
ASF GitHub Bot commented on STORM-1925:
---
GitHub user HeartSaVioR opened a pull request:
GitHub user HeartSaVioR opened a pull request:
https://github.com/apache/storm/pull/1514
STORM-1925 Remove Nimbus thrift call from Nimbus itself (1.x)
* Nimbus fails to start in secure mode since authrization is not passed
* Extract the logic of getClusterInfo to new function
[
https://issues.apache.org/jira/browse/STORM-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15346073#comment-15346073
]
ASF GitHub Bot commented on STORM-1925:
---
GitHub user HeartSaVioR opened a pull request:
GitHub user HeartSaVioR opened a pull request:
https://github.com/apache/storm/pull/1513
STORM-1925 Remove Nimbus thrift call from Nimbus itself
* Nimbus fails to start in secure mode since authrization is not passed
Extract the logic of getClusterInfo to new function
Hi!
Thanks for your pointers!
I want to make sure the I/O message queue also being pined together with the
corresponding executor, is it possible to do in Storm?
Follow Bobby's "easier solution" suggestion, in a machine with multiple CPU
sockets, if I pin the executor thread to one CPU socket
[
https://issues.apache.org/jira/browse/STORM-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15345952#comment-15345952
]
Jungtaek Lim commented on STORM-1925:
-
Harsha pointed out I'm calling Nimbus thrift API inside of
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1468
Here's my understanding regarding this script.
> main()
* get latest branch (highest version) from github mirror
* it assumes that prefix of release branch is `release
[
https://issues.apache.org/jira/browse/STORM-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15345930#comment-15345930
]
ASF GitHub Bot commented on STORM-1885:
---
Github user HeartSaVioR commented on the issue:
[
https://issues.apache.org/jira/browse/STORM-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim updated STORM-1925:
Component/s: storm-core
> Nimbus fails to start in secure mode
>
[
https://issues.apache.org/jira/browse/STORM-1925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim updated STORM-1925:
Affects Version/s: 1.1.0
2.0.0
> Nimbus fails to start in secure mode
>
Sriharsha Chintalapani created STORM-1925:
-
Summary: Nimbus fails to start in secure mode
Key: STORM-1925
URL: https://issues.apache.org/jira/browse/STORM-1925
Project: Apache Storm
68 matches
Mail list logo