[GitHub] storm issue #1693: [STORM-1961] Stream api for storm core use cases

Github user satishd commented on the issue: https://github.com/apache/storm/pull/1693 @arunmahadevan I was saying we should not hold on this PR till Beam runner API is tried with these APIs. We should review these APIs soon and these may remain experimental for couple of minor

[GitHub] storm issue #1693: [STORM-1961] Stream api for storm core use cases

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1693 For me this stream API is not only for supporting Beam. This is what Storm needed to have even before Beam is open-sourced. We may want to label this API to experiment or unstable or something,

[GitHub] storm issue #1736: STORM-1446 Compile the Calcite logical plan to Storm Trid...

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1736 Fixed some bugs, and renamed classes to reflect more specific. Unit test passes and manually tested. --- If your project is set up for it, you can reply to this email and have your reply

[GitHub] storm issue #1693: [STORM-1961] Stream api for storm core use cases

Github user arunmahadevan commented on the issue: https://github.com/apache/storm/pull/1693 @satishd right now its more of a prototype proof of concept for the proposed apis, not the final version. Once the beam api solidifies we can have a separate discussion to identify the gaps,

[GitHub] storm issue #1693: [STORM-1961] Stream api for storm core use cases

Github user satishd commented on the issue: https://github.com/apache/storm/pull/1693 It is better to discuss these APIs before working on Beam runner prototypes. Lets not jump on using these APIs to work on runner. Beam API is currently changing and we should discuss those API

[GitHub] storm issue #1693: [STORM-1961] Stream api for storm core use cases

Github user HeartSaVioR commented on the issue: https://github.com/apache/storm/pull/1693 @arunmahadevan I'm in the middle of reviewing updated design doc again. Since I've read it once so there will be no outstanding comments, but just would like to check again. Btw, I

Re: [DISCUSS] Feature Branch for Apache Beam Runner

+1, waiting for that. :) Currently,there are API changes going on in Beam. It seem they plan to get that done by the end of 2016. ~Satish. On Wed, Oct 19, 2016 at 9:19 PM, Bobby Evans wrote: > +1 - Bobby > > On Wednesday, October 19, 2016 10:30 AM, Arun

Re: [DISCUSS] Feature Branch for Apache Beam Runner

+1 - Bobby On Wednesday, October 19, 2016 10:30 AM, Arun Mahadevan wrote: +1 On 10/19/16, 8:58 PM, "P. Taylor Goetz" wrote: >If there are no objections, I’d like to create the feature branch and push >what I have so far. I’ve not had too much

Re: [DISCUSS] Feature Branch for Apache Beam Runner

+1 On 10/19/16, 8:58 PM, "P. Taylor Goetz" wrote: >If there are no objections, I’d like to create the feature branch and push >what I have so far. I’ve not had too much time lately to work on it, but >other’s have expressed interest in contributing so I’d like to make it

Re: [DISCUSS] Feature Branch for Apache Beam Runner

If there are no objections, I’d like to create the feature branch and push what I have so far. I’ve not had too much time lately to work on it, but other’s have expressed interest in contributing so I’d like to make it available. -Taylor > On Sep 19, 2016, at 11:15 AM, Bobby Evans

[GitHub] storm issue #1693: [STORM-1961] Stream api for storm core use cases

Github user ptgoetz commented on the issue: https://github.com/apache/storm/pull/1693 @arunmahadevan I will review. Before you start working on a prototype beam runner, let me push what I have to a feature branch. I have a fair amount of the basic scaffolding you would need. --- If

[GitHub] storm issue #1693: [STORM-1961] Stream api for storm core use cases

Github user arunmahadevan commented on the issue: https://github.com/apache/storm/pull/1693 Updated doc - https://docs.google.com/document/d/1Ew7uFF1UJ6e_zq0t4bM6A9auuEaArviAjjWYSpVFqPY/edit?usp=sharing Pinging for reviews and feedback. Its a big patch mostly due the

[GitHub] storm pull request #1739: STORM-1443 Support customizing parallelism in Stor...

GitHub user HeartSaVioR opened a pull request: https://github.com/apache/storm/pull/1739 STORM-1443 Support customizing parallelism in StormSQL * Add 'PARALLELISM' to table definition * default value is 1 * Set parallelism to new stream while creating stream with scan