[
https://issues.apache.org/jira/browse/STORM-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim updated STORM-2075:
Description:
This epic tracks the effort of the phase III development of StormSQL.
For now Storm
[
https://issues.apache.org/jira/browse/STORM-1444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15454308#comment-15454308
]
Jungtaek Lim commented on STORM-1444:
-
It might need to have different approach.
Storm SQL is
Github user vesense commented on the issue:
https://github.com/apache/storm/pull/1665
Thanks @priyank5485 @abellina I think I have addressed your comments.
---
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
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1666
Great. Thanks for the quick update. +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 manuzhang commented on the issue:
https://github.com/apache/storm/pull/1666
@HeartSaVioR Updated. I use "Kafka sink table" instead of "consumer" to
avoid confusing with kafka consumer. And I don't think `TBLPROPERTIES` is an
option for "table as a producer" so I leave
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1648
@revans2 This is also a fix for STORM-2059. please review this.
---
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
Github user hackerwin7 commented on the issue:
https://github.com/apache/storm/pull/1660
the fix is worked to build
---
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-2074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xin Wang updated STORM-2074:
Description: storm-kafka-monitor will throw an NPE when __--zk-node__ value
does not exist. this is not
Github user vesense commented on a diff in the pull request:
https://github.com/apache/storm/pull/1665#discussion_r77109600
--- Diff:
external/storm-kafka-monitor/src/main/java/org/apache/storm/kafka/monitor/KafkaOffsetLagUtil.java
---
@@ -373,16 +377,20 @@ private static Options
Jungtaek Lim created STORM-2075:
---
Summary: Storm SQL Phase III
Key: STORM-2075
URL: https://issues.apache.org/jira/browse/STORM-2075
Project: Apache Storm
Issue Type: Epic
Github user vesense commented on a diff in the pull request:
https://github.com/apache/storm/pull/1665#discussion_r77107687
--- Diff:
external/storm-kafka-monitor/src/main/java/org/apache/storm/kafka/monitor/KafkaOffsetLagUtil.java
---
@@ -373,16 +377,20 @@ private static Options
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1666
+1 except minor documentation issue.
---
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/1666#discussion_r77107492
--- Diff: docs/storm-sql.md ---
@@ -104,21 +104,22 @@ Let's say there is a Kafka stream that represents the
transactions of orders. Ea
The user can
Github user abellina commented on a diff in the pull request:
https://github.com/apache/storm/pull/1665#discussion_r77107294
--- Diff:
external/storm-kafka-monitor/src/main/java/org/apache/storm/kafka/monitor/KafkaOffsetLagUtil.java
---
@@ -373,16 +377,20 @@ private static
Github user vesense commented on a diff in the pull request:
https://github.com/apache/storm/pull/1665#discussion_r77106883
--- Diff:
external/storm-kafka-monitor/src/main/java/org/apache/storm/kafka/monitor/KafkaOffsetLagUtil.java
---
@@ -89,6 +89,10 @@ public static void main
[
https://issues.apache.org/jira/browse/STORM-1949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15453966#comment-15453966
]
Zhuo Liu commented on STORM-1949:
-
Hi [~roshan_naik], [~abellina] has
GitHub user manuzhang opened a pull request:
https://github.com/apache/storm/pull/1666
STORM-1459: allow not specifying producer properties in read-only Kafâ¦
â¦ka table in StormSQL
You can merge this pull request into a Git repository by running:
$ git pull
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1565
I think we have to make sure that users can run example topologies with
local and also remote.
(Yes these modules are just examples but 'runnable' examples.)
So it might be better to
Github user HeartSaVioR commented on a diff in the pull request:
https://github.com/apache/storm/pull/1565#discussion_r77088437
--- Diff: examples/storm-mqtt-examples/pom.xml ---
@@ -24,18 +24,24 @@
storm-mqtt-examples
-
-org.apache.storm
-
[
https://issues.apache.org/jira/browse/STORM-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim resolved STORM-2056.
-
Resolution: Fixed
Fix Version/s: 1.0.3
1.1.0
2.0.0
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/1659
---
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 asfgit closed the pull request at:
https://github.com/apache/storm/pull/1658
---
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
[
https://issues.apache.org/jira/browse/STORM-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim resolved STORM-1646.
-
Resolution: Fixed
Fix Version/s: 1.0.3
1.1.0
2.0.0
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1662
@ppoulosk
Could you rebase this into master and squash commits into one? I guess
discarding first commit would be good.
Also please add STORM-1344 as prefix to commit message since we
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1662
OK. Checked changeset doesn't affect the build result. Nice work. +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
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1661
From JIRA comment @revans2 said he fixed this issue from Supervisor V2
patch.
@revans2 Since we saw builds failing (high chance from my dev.) how about
addressing build issue before
Canceling this vote so the fix for STORM-2042 can be included in the next
release.
-Taylor
> On Aug 26, 2016, at 12:00 PM, Harsha Chintalapani wrote:
>
> We need to get this patch in for 0.10 release
> https://github.com/apache/storm/pull/1645
>
> Thanks,
> Harsha
>
> On
This vote is now closed and passes with 3 binding +1 votes, and no +0 or -1
votes.
Vote tally:
+1:
P. Taylor Goetz
Jungtaek Lim
Bobby Evans
-Taylor
> On Aug 15, 2016, at 4:10 PM, P. Taylor Goetz wrote:
>
> This is a call to vote on releasing Apache Storm 0.9.7 (rc1).
>
Github user priyank5485 commented on a diff in the pull request:
https://github.com/apache/storm/pull/1665#discussion_r77034491
--- Diff:
external/storm-kafka-monitor/src/main/java/org/apache/storm/kafka/monitor/KafkaOffsetLagUtil.java
---
@@ -373,16 +377,20 @@ private static
Github user priyank5485 commented on a diff in the pull request:
https://github.com/apache/storm/pull/1665#discussion_r77033989
--- Diff:
external/storm-kafka-monitor/src/main/java/org/apache/storm/kafka/monitor/KafkaOffsetLagUtil.java
---
@@ -89,6 +89,10 @@ public static void
Github user abellina commented on the issue:
https://github.com/apache/storm/pull/1661
+1 thanks @ppoulosk
---
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
Github user abhishekagarwal87 commented on the issue:
https://github.com/apache/storm/pull/1565
+1 Post the conflicts merge.
@HeartSaVioR - can you also take a look?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user vesense commented on the issue:
https://github.com/apache/storm/pull/1665
this should be merged into 1.x-branch.
---
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 revans2 commented on the issue:
https://github.com/apache/storm/pull/1642
@HeartSaVioR take your time. I want to be sure that I have plenty of
eyeballs looking at this. We are doing this mostly because we started to run
into a lot of race conditions in the supervisor.
GitHub user vesense opened a pull request:
https://github.com/apache/storm/pull/1665
STORM-2074: fix storm-kafka-monitor NPE bug
https://issues.apache.org/jira/browse/STORM-2074
You can merge this pull request into a Git repository by running:
$ git pull
Github user ppoulosk commented on the issue:
https://github.com/apache/storm/pull/1662
Fixed. Re-ran tests. 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 does not have this feature
enabled and
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1642
I'm still reviewing this. Nice work to refactor to introduce greater
readability. Will leave comment here once I'm done with first pass.
---
If your project is set up for it, you can reply to
Github user ppoulosk commented on the issue:
https://github.com/apache/storm/pull/1662
@HeartSaVioR, @abellina, will fix as you suggest.
---
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
Github user ppoulosk commented on the issue:
https://github.com/apache/storm/pull/1661
Coded fix, retested, and pushed. 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 does not have this feature
Github user HeartSaVioR commented on a diff in the pull request:
https://github.com/apache/storm/pull/1642#discussion_r77000695
--- Diff:
storm-core/src/jvm/org/apache/storm/daemon/supervisor/BasicContainer.java ---
@@ -0,0 +1,628 @@
+/**
+ * Licensed to the Apache
Github user ppoulosk commented on a diff in the pull request:
https://github.com/apache/storm/pull/1661#discussion_r76999135
--- Diff: storm-core/test/clj/org/apache/storm/nimbus_test.clj ---
@@ -1218,8 +1218,16 @@
(submit-local-topology nimbus "t1" {} topology)
Github user revans2 commented on a diff in the pull request:
https://github.com/apache/storm/pull/1642#discussion_r76997296
--- Diff:
storm-core/src/jvm/org/apache/storm/daemon/supervisor/AdvancedFSOps.java ---
@@ -0,0 +1,319 @@
+/**
+ * Licensed to the Apache Software
Xin Wang created STORM-2074:
---
Summary: NPE bug in storm-kafka-monitor
Key: STORM-2074
URL: https://issues.apache.org/jira/browse/STORM-2074
Project: Apache Storm
Issue Type: Bug
Github user HeartSaVioR commented on a diff in the pull request:
https://github.com/apache/storm/pull/1642#discussion_r76991771
--- Diff:
storm-core/src/jvm/org/apache/storm/daemon/supervisor/AdvancedFSOps.java ---
@@ -0,0 +1,319 @@
+/**
+ * Licensed to the Apache Software
Github user revans2 commented on the issue:
https://github.com/apache/storm/pull/1660
+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 feature
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/1638
---
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
[
https://issues.apache.org/jira/browse/STORM-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15452246#comment-15452246
]
Robert Joseph Evans commented on STORM-2071:
I replaced the sleep with
{code}
(defn
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1638
+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 vesense commented on the issue:
https://github.com/apache/storm/pull/1565
@abhishekagarwal87 is this should be continue?
---
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-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15452239#comment-15452239
]
Robert Joseph Evans commented on STORM-2071:
I found and fixed this in my supervisor v2 patch.
Github user abellina commented on the issue:
https://github.com/apache/storm/pull/1638
ð
---
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-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans reassigned STORM-2071:
--
Assignee: Robert Joseph Evans
> nimbus-test test-leadership failing with
Github user vesense commented on the issue:
https://github.com/apache/storm/pull/1603
@darionyaphet two important fixes for snappy compression. please take a
look the above link first, thanks.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user vesense commented on the issue:
https://github.com/apache/storm/pull/1638
hi @HeartSaVioR Done.
---
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
[
https://issues.apache.org/jira/browse/STORM-1344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15452218#comment-15452218
]
Robert Joseph Evans commented on STORM-1344:
Do you have a patch for that? I can see it being
Hi everyone,
Is it easier to specify in which tcp port the tasks (threads) will be
assigned?Any API can help to do that?
Thank You--Regards
[
https://issues.apache.org/jira/browse/STORM-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim resolved STORM-2039.
-
Resolution: Fixed
Fix Version/s: 1.0.3
1.1.0
2.0.0
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/1627
---
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 asfgit closed the pull request at:
https://github.com/apache/storm/pull/1632
---
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/1627
+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 HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1638
@vesense Nice finding. I'll merge once you rebase this to current master.
Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1613
@ThijsMergaert
Sorry to comment too late.
I'm not sure how much python users use Storm python multi-lang directly,
and what's more preferred version, 2 vs 3. If many users still
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/1614
---
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 asfgit closed the pull request at:
https://github.com/apache/storm/pull/1615
---
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 asfgit closed the pull request at:
https://github.com/apache/storm/pull/1612
---
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/1615
+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 HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1612
+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 HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1614
+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-2042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim updated STORM-2042:
Fix Version/s: 0.10.3
> Nimbus client connections not closed properly causing connection leaks
>
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/1645
---
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
FYI: Just worked to have one -
http://issues.apache.org/jira/browse/STORM-2072
This adds map and flatMap to have additional parameter: outputFields. If
outputFields are specified, it replaces origin fields with output fields.
- Jungtaek Lim (HeartSaVioR)
2016년 8월 31일 (수) 오전 10:27, Jungtaek Lim
[
https://issues.apache.org/jira/browse/STORM-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim resolved STORM-2064.
-
Resolution: Fixed
Fix Version/s: 1.0.3
1.1.0
2.0.0
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/1651
---
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 asfgit closed the pull request at:
https://github.com/apache/storm/pull/1650
---
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 sakanaou commented on the issue:
https://github.com/apache/storm/pull/1480
Closed as requested due to STORM-2016.
---
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 sakanaou closed the pull request at:
https://github.com/apache/storm/pull/1480
---
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/1645
+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 HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1650
+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 HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1651
+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-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim resolved STORM-2063.
-
Resolution: Fixed
Fix Version/s: 1.0.3
1.1.0
2.0.0
Github user asfgit closed the pull request at:
https://github.com/apache/storm/pull/1653
---
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 asfgit closed the pull request at:
https://github.com/apache/storm/pull/1652
---
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
[
https://issues.apache.org/jira/browse/STORM-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jungtaek Lim closed STORM-1703.
---
Resolution: Duplicate
> In local mode, process is not shutting down clearly
>
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1659
+1 Nice work.
---
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
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1662
@abellina I got what you are saying.
@ppoulosk Let's remove test.sql and relevant setting from pom.xml since
JdbcClientTest is already in charge to create table.
---
If your project is set
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1661
+1 once comments from @abellina are addressed. Nice finding.
---
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
Github user HeartSaVioR commented on a diff in the pull request:
https://github.com/apache/storm/pull/1661#discussion_r76932681
--- Diff: storm-core/test/clj/org/apache/storm/nimbus_test.clj ---
@@ -1218,8 +1218,16 @@
(submit-local-topology nimbus "t1" {}
Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/1662
We need to ensure that created table from unit tests will be dropped when
cleaning up tests. Removing data directory would be also OK.
---
If your project is set up for it, you can reply to
88 matches
Mail list logo