[GitHub] storm issue #1655: STORM-2067 Fix "array element type mismatch" from compute...

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1655 +1 from STORM-2057 #1656 (by @arunmahadevan ) --- 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] storm pull request #1656: STORM-2057 Support JOIN statement in Storm SQL

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1656 --- 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] storm pull request #1655: STORM-2067 Fix "array element type mismatch" from ...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1655 --- 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] storm issue #1656: STORM-2057 Support JOIN statement in Storm SQL

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1656 Thanks @arunmahadevan for reviewing. Since I've also addressed style review comments I'll just go on merging this. --- If your project is set up for it, you can reply to this email and have

[GitHub] storm pull request #1682: STORM-2089 Replace Consumer of ISqlTridentDataSour...

GitHub user HeartSaVioR opened a pull request: https://github.com/apache/storm/pull/1682 STORM-2089 Replace Consumer of ISqlTridentDataSource with SqlTridentConsumer * issue link: https://issues.apache.org/jira/browse/STORM-2089 This is for handling INSERT for tuples as

[GitHub] storm issue #1679: STORM-2087: storm-kafka-client - tuples not always being ...

Github user jfenc91 commented on the issue: https://github.com/apache/storm/pull/1679 A larger refactor here is probably needed to make this more performant. These changes understandably seem to make the spout struggle to get the processing tuple count anywhere near the max spout

Re: Flux exception while upgrading to Storm 1.0.2

Hi Manu, I do not see any 0.10.0 versions being downloaded in my ~/.m2 repo: ls ~/.m2/repository/org/apache/storm/* ~/.m2/repository/org/apache/storm/flux: 1.0.2 ~/.m2/repository/org/apache/storm/flux-core: 1.0.2 ~/.m2/repository/org/apache/storm/storm: 1.0.2

Re: Flux exception while upgrading to Storm 1.0.2

Hi, Could you share your maven file ? When running `mvn package`, you should see what and which version of jar files are included ? That may give you a hint. Thanks, Manu On Tue, Sep 13, 2016 at 6:50 AM S G wrote: > From the >

Re: Flux exception while upgrading to Storm 1.0.2

>From the https://github.com/apache/storm/tree/1.0.x-branch/external/storm-kafka docs, "This means that pre 1.0 kafka spouts will not work with Storm versions 1.0 and higher. While running topologies in Storm version 1.0 and higher, it must be ensured that the storm-kafka version is at least 1.0.

Re: Flux exception while upgrading to Storm 1.0.2

Can anyone help with this? I tried relocating classes too during shading as: backtype.storm org.apache.storm storm.trident org.apache.storm.trident org.apache.thrift7

Re: JIRI Notifications Moved to iss...@storm.apache.org

Nice work. Will Github notification (posted to dev@) be also moved to issues@? Or will keep posted to dev@? On 2016년 9월 13일 (화) at 오전 6:00 P. Taylor Goetz wrote: > Infra has now moved JIRA notifications from dev@storm.apache.org to > issues.storm.apache.org. > > If you would

JIRI Notifications Moved to iss...@storm.apache.org

Infra has now moved JIRA notifications from dev@storm.apache.org to issues.storm.apache.org . If you would like to continue to receive JIRA notifications, you should subscribe to that list by sending an email to:

[GitHub] storm issue #1680: Minor typos in documentation

Github user redsanket commented on the issue: https://github.com/apache/storm/pull/1680 +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

Re: Clojure to Java Migration (was: How does Storm's OutputCollector work?)

> On Sep 12, 2016, at 3:26 PM, S G wrote: > > Just curious, how much of the code-base is planned to be moved away from > clojure to Java? Ultimately all the Clojure code will move to Java. The initial focus is to get the main (i.e. non-test) code converted before

Re: How does Storm's OutputCollector work?

Thanks a lot Manu, Those pointers are of great help. Can you also help with http://stackoverflow.com/questions/39456590/is-nimbus-host-a-valid-option-in-storm-1-0-2-version ? On Mon, Sep 12, 2016 at 12:26 PM, S G wrote: > Thx Bobby, > Just curious, how much of the

Re: How does Storm's OutputCollector work?

Thx Bobby, Just curious, how much of the code-base is planned to be moved away from clojure to Java? When do we plan to make a release for the Java-based code? On Mon, Sep 12, 2016 at 6:21 AM, Bobby Evans wrote: > Manu Zhang is correct in his answer. The main

Flux exception while upgrading to Storm 1.0.2

Hi, We are upgrading to Storm 1.0.2 and have done all the package name changes. grep -ri backtype in our code repo returns nothing. Yet on deploying the jar to Storm, following error is seen: storm/storm_installed/apache-storm-1.0.2/bin/storm \ jar \ $jarFile \ org.apache.storm.flux.Flux \

[jira] [Created] (STORM-2091) storm-kafka-client, NoSuchMethod on KafkaConsumer.subscribe

Pierre Padrixe created STORM-2091: - Summary: storm-kafka-client, NoSuchMethod on KafkaConsumer.subscribe Key: STORM-2091 URL: https://issues.apache.org/jira/browse/STORM-2091 Project: Apache Storm

[jira] [Commented] (STORM-2090) Add integration test for storm windowing

[ https://issues.apache.org/jira/browse/STORM-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484786#comment-15484786 ] Raghav Kumar Gautam commented on STORM-2090: For now I am using vagrant setup for debugging

[jira] [Commented] (STORM-2090) Add integration test for storm windowing

[ https://issues.apache.org/jira/browse/STORM-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484781#comment-15484781 ] Raghav Kumar Gautam commented on STORM-2090: It seems to get logs from travis ci we have

[jira] [Created] (STORM-2090) Add integration test for storm windowing

Raghav Kumar Gautam created STORM-2090: -- Summary: Add integration test for storm windowing Key: STORM-2090 URL: https://issues.apache.org/jira/browse/STORM-2090 Project: Apache Storm

Re: [VOTE] Release Apache Storm 0.10.2 (rc2)

This vote is now closed, and passes with 4 binding +1 votes and no 0 or -1 votes. Vote tally: +1: P. Taylor Goetz Bobby Evans Jungtaek Lim Satish Duggana Thanks to everyone who took the time to vote. -Taylor > On Sep 2, 2016, at 3:40 PM, P. Taylor Goetz wrote: > > This

[GitHub] storm issue #1661: [STORM-2071] Add in retry after rebalance in unit test

Github user ppoulosk commented on the issue: https://github.com/apache/storm/pull/1661 @HeartSaVioR @revans2 I have no preference which solution gets pulled in first. I fixed the comment, retested, squashed the three commits into one and pushed it to my branch.

[jira] [Created] (STORM-2089) Replace Consumer of ISqlTridentDataSource with StateFactory and StateUpdater

Jungtaek Lim created STORM-2089: --- Summary: Replace Consumer of ISqlTridentDataSource with StateFactory and StateUpdater Key: STORM-2089 URL: https://issues.apache.org/jira/browse/STORM-2089 Project:

Re: How does Storm's OutputCollector work?

Manu Zhang is correct in his answer.  The main reason why you cannot find a class that implements that interface is because in all released versions of storm the code was written in clojure, so it is hidden away for people who are used to just java. - Bobby On Monday, September 12, 2016

[jira] [Commented] (STORM-2075) Storm SQL Phase III

[ https://issues.apache.org/jira/browse/STORM-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15484071#comment-15484071 ] Jungtaek Lim commented on STORM-2075: - Below is Trident support for external modules. || module ||

[GitHub] storm pull request #1681: STORM-1444 Support EXPLAIN statement in StormSQL

GitHub user HeartSaVioR opened a pull request: https://github.com/apache/storm/pull/1681 STORM-1444 Support EXPLAIN statement in StormSQL * when '--explain' is specified to topology name, activate explain mode * when explain mode is activated, it analyzes each query statement,