Re: Error while building locally

Yes I verified, it is 2.0.0-SNAPSHOT only. I am not able to find why is it looking for 2.0.0. On Sat, Oct 1, 2016 at 7:58 AM, Jungtaek Lim wrote: > That's really odd. Could you open pom.xml and check the version? Master > branch is at 2.0.0-SNAPSHOT. > > 2016년 9월 30일 (금) 오전 1:29, Sonu B 님이 작성:

[GitHub] storm pull request #1654: STORM-2066: make error message in IsolatedPool.jav...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1654 --- 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] storm issue #1654: STORM-2066: make error message in IsolatedPool.java more ...

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1654 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, or

[GitHub] storm pull request #1668: STORM-2040 Fix bug on assert-can-serialize

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1668 --- 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] storm pull request #1646: STORM-1870 Allow FluxShellBolt/Spout set custom "c...

Github user asfgit closed the pull request at: https://github.com/apache/storm/pull/1646 --- 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] storm issue #1697: STORM-2018: Supervisor V2

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1697 I found two issues, but other than that manual tests passed. Code review is already done from PR for master branch. +1 once these are resolved. --- If your project is set up for it, you can repl

[GitHub] storm pull request #1697: STORM-2018: Supervisor V2

Github user HeartSaVioR commented on a diff in the pull request: https://github.com/apache/storm/pull/1697#discussion_r81442669 --- Diff: storm-core/src/jvm/org/apache/storm/command/HealthCheck.java --- @@ -0,0 +1,126 @@ +/** --- End diff -- This file seems to be cl

Re: Error while building locally

That's really odd. Could you open pom.xml and check the version? Master branch is at 2.0.0-SNAPSHOT. 2016년 9월 30일 (금) 오전 1:29, Sonu B 님이 작성: > Following is the result of git status command > > > git status > > ---

[GitHub] storm issue #1697: STORM-2018: Supervisor V2

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1697 While running build in storm-core I found that null/storm-local directory is created in storm-core. Maybe there's a case base path is set to null. --- If your project is set up for it, you can r

FYI: backported excluding logs to rat plugin

It's fixed to master branch but not other branches. I backported this to 1.x and 1.0.x branch and pushed. cherry-picked commit is 9165b603985c0c158821cd5a20e6c509ee63342a Thanks, Jungtaek Lim (HeartSaVioR

[GitHub] storm issue #1697: STORM-2018: Supervisor V2

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1697 I just cherry-picked commit which excludes logs from RAT. It's merged to master but was part of port work so didn't port back. --- If your project is set up for it, you can reply to this email a

Re: [DISCUSS] Release Storm 1.1.0

Personally, merging and porting back to three branches are painful enough, especially we don't have merging script and having verbose process (I mean CHANGELOG). It would be better if merging process is automated (by running script or so), so I'd +1 to revisit Harsha's suggestion (adopting Kafka me

[GitHub] storm issue #1591: STORM-1038: Upgrade netty to 4.x in 1.x-branch

Github user hsun-cnnxty commented on the issue: https://github.com/apache/storm/pull/1591 Tests are done to compare following two code bases: - baseline: current head of 1.x-branch (62476f5237a72938c1f0d3fe65dbcdc446a2bd12) - netty 4.1.x: 1.x-branch-netty4 (dd96d9f4ba5b8da8d688

[GitHub] storm issue #1591: STORM-1038: Upgrade netty to 4.x in 1.x-branch

Github user hsun-cnnxty commented on the issue: https://github.com/apache/storm/pull/1591 @HeartSaVioR I rebased to 1.x-branch and also squashed the commits. Will attached the performance test results soon. --- If your project is set up for it, you can reply to this email and ha

[GitHub] storm issue #1720: STORM-1546: Adding Read and Write Aggregations for Pacema...

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

[GitHub] storm issue #1710: STORM-1546: Adding Read and Write Aggregations for Pacema...

Github user knusbaum commented on the issue: https://github.com/apache/storm/pull/1710 @d2r @revans2 Any additional 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 does not have this feature enab

[GitHub] storm issue #1646: STORM-1870 Allow FluxShellBolt/Spout set custom "componen...

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

Re: [DISCUSS] Release Storm 1.1.0

Sounds good to me.  It would be nice to get some of the new features out. Do we expect to maintain both 1.0.x and 1.1.x lines with bug fixes?  And if so for how long do we want to do this for? - Bobby On Thursday, September 29, 2016 7:35 PM, Jungtaek Lim wrote: Hi devs, It's been 5 m

[GitHub] storm pull request #1721: Update storm kafka docs.

GitHub user aandis opened a pull request: https://github.com/apache/storm/pull/1721 Update storm kafka docs. [docs/storm-kafka.md](https://github.com/apache/storm/blob/d88558237f37de87d81fad0be7d51042328c615e/docs/storm-kafka.md) is out of date. This updates it to be the same as [