[jira] [Commented] (GEARPUMP-217) Add SQL support
[ https://issues.apache.org/jira/browse/GEARPUMP-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16139580#comment-16139580 ] ASF GitHub Bot commented on GEARPUMP-217: - Github user manuzhang commented on the issue: https://github.com/apache/incubator-gearpump/pull/219 This PR has been merged. You can close now. > Add SQL support > > > Key: GEARPUMP-217 > URL: https://issues.apache.org/jira/browse/GEARPUMP-217 > Project: Apache Gearpump > Issue Type: New Feature > Components: streaming >Affects Versions: 0.8.1 >Reporter: Manu Zhang >Assignee: Buddhi Ayesha > Labels: gsoc2017, mentor > > SQL support will allow those unfamiliar with Scala/Java to use Gearpump. I > propose to build SQL layer with Apache Calcite because > 1. It has done the hard job of parsing, translating logical plan to physical > plan and optimizing. > 2. It is under active development and has a great community. > 3. It's proved to be a good solution since Apache Storm, Apache Flink and > Apache Samza all build their Streaming SQL with Apache Calcite > Note SQL here actually means Streaming SQL dialects supported by Calcite > (check reference 1 and 2). Please checkout reference 3 for an example > implementation. > The physical plan will be translated to Gearpump high level DSL. > References: > 1. http://www.slideshare.net/julianhyde/streaming-sql > 2. https://calcite.apache.org/docs/stream.html > 3. https://github.com/milinda/samza-sql -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (GEARPUMP-217) Add SQL support
[ https://issues.apache.org/jira/browse/GEARPUMP-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16139579#comment-16139579 ] ASF GitHub Bot commented on GEARPUMP-217: - Github user manuzhang commented on the issue: https://github.com/apache/incubator-gearpump/pull/219 LGTM > Add SQL support > > > Key: GEARPUMP-217 > URL: https://issues.apache.org/jira/browse/GEARPUMP-217 > Project: Apache Gearpump > Issue Type: New Feature > Components: streaming >Affects Versions: 0.8.1 >Reporter: Manu Zhang >Assignee: Buddhi Ayesha > Labels: gsoc2017, mentor > > SQL support will allow those unfamiliar with Scala/Java to use Gearpump. I > propose to build SQL layer with Apache Calcite because > 1. It has done the hard job of parsing, translating logical plan to physical > plan and optimizing. > 2. It is under active development and has a great community. > 3. It's proved to be a good solution since Apache Storm, Apache Flink and > Apache Samza all build their Streaming SQL with Apache Calcite > Note SQL here actually means Streaming SQL dialects supported by Calcite > (check reference 1 and 2). Please checkout reference 3 for an example > implementation. > The physical plan will be translated to Gearpump high level DSL. > References: > 1. http://www.slideshare.net/julianhyde/streaming-sql > 2. https://calcite.apache.org/docs/stream.html > 3. https://github.com/milinda/samza-sql -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] incubator-gearpump issue #219: [GEARPUMP-217] Remove irrelevant files, Updat...
Github user codecov-io commented on the issue: https://github.com/apache/incubator-gearpump/pull/219 # [Codecov](https://codecov.io/gh/apache/incubator-gearpump/pull/219?src=pr=h1) Report > :exclamation: No coverage uploaded for pull request base (`sql@1cf87bf`). [Click here to learn what that means](https://docs.codecov.io/docs/error-reference#section-missing-base-commit). > The diff coverage is `n/a`. ```diff @@ Coverage Diff @@ ## sql #219 +/- ## == Coverage ? 68.89% == Files ? 192 Lines ? 6108 Branches ? 363 == Hits ? 4208 Misses ? 1900 Partials ?0 ``` --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (GEARPUMP-217) Add SQL support
[ https://issues.apache.org/jira/browse/GEARPUMP-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16139526#comment-16139526 ] ASF GitHub Bot commented on GEARPUMP-217: - Github user codecov-io commented on the issue: https://github.com/apache/incubator-gearpump/pull/219 # [Codecov](https://codecov.io/gh/apache/incubator-gearpump/pull/219?src=pr=h1) Report > :exclamation: No coverage uploaded for pull request base (`sql@1cf87bf`). [Click here to learn what that means](https://docs.codecov.io/docs/error-reference#section-missing-base-commit). > The diff coverage is `n/a`. ```diff @@ Coverage Diff @@ ## sql #219 +/- ## == Coverage ? 68.89% == Files ? 192 Lines ? 6108 Branches ? 363 == Hits ? 4208 Misses ? 1900 Partials ?0 ``` > Add SQL support > > > Key: GEARPUMP-217 > URL: https://issues.apache.org/jira/browse/GEARPUMP-217 > Project: Apache Gearpump > Issue Type: New Feature > Components: streaming >Affects Versions: 0.8.1 >Reporter: Manu Zhang >Assignee: Buddhi Ayesha > Labels: gsoc2017, mentor > > SQL support will allow those unfamiliar with Scala/Java to use Gearpump. I > propose to build SQL layer with Apache Calcite because > 1. It has done the hard job of parsing, translating logical plan to physical > plan and optimizing. > 2. It is under active development and has a great community. > 3. It's proved to be a good solution since Apache Storm, Apache Flink and > Apache Samza all build their Streaming SQL with Apache Calcite > Note SQL here actually means Streaming SQL dialects supported by Calcite > (check reference 1 and 2). Please checkout reference 3 for an example > implementation. > The physical plan will be translated to Gearpump high level DSL. > References: > 1. http://www.slideshare.net/julianhyde/streaming-sql > 2. https://calcite.apache.org/docs/stream.html > 3. https://github.com/milinda/samza-sql -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] incubator-gearpump pull request #219: [GEARPUMP-217] Remove irrelevant files...
GitHub user buddhiayesha2015 opened a pull request: https://github.com/apache/incubator-gearpump/pull/219 [GEARPUMP-217] Remove irrelevant files, Update README.md Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the commit message is formatted like: `[GEARPUMP-] Meaningful description of pull request` - [ ] Make sure tests pass via `sbt clean test`. - [ ] Make sure old documentation affected by the pull request has been updated and new documentation added for new functionality. You can merge this pull request into a Git repository by running: $ git pull https://github.com/GearGSoC/incubator-gearpump sql Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-gearpump/pull/219.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #219 commit cb509674b3507e5224a3c3a442b7030f469f4ebb Author: Buddhi AyeshaDate: 2017-08-23T16:23:24Z [GEARPUMP-217] Remove irrelevant files, Update README.md --- 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 enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (GEARPUMP-217) Add SQL support
[ https://issues.apache.org/jira/browse/GEARPUMP-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16139517#comment-16139517 ] ASF GitHub Bot commented on GEARPUMP-217: - GitHub user buddhiayesha2015 opened a pull request: https://github.com/apache/incubator-gearpump/pull/219 [GEARPUMP-217] Remove irrelevant files, Update README.md Be sure to do all of the following to help us incorporate your contribution quickly and easily: - [ ] Make sure the commit message is formatted like: `[GEARPUMP-] Meaningful description of pull request` - [ ] Make sure tests pass via `sbt clean test`. - [ ] Make sure old documentation affected by the pull request has been updated and new documentation added for new functionality. You can merge this pull request into a Git repository by running: $ git pull https://github.com/GearGSoC/incubator-gearpump sql Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-gearpump/pull/219.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #219 commit cb509674b3507e5224a3c3a442b7030f469f4ebb Author: Buddhi AyeshaDate: 2017-08-23T16:23:24Z [GEARPUMP-217] Remove irrelevant files, Update README.md > Add SQL support > > > Key: GEARPUMP-217 > URL: https://issues.apache.org/jira/browse/GEARPUMP-217 > Project: Apache Gearpump > Issue Type: New Feature > Components: streaming >Affects Versions: 0.8.1 >Reporter: Manu Zhang >Assignee: Buddhi Ayesha > Labels: gsoc2017, mentor > > SQL support will allow those unfamiliar with Scala/Java to use Gearpump. I > propose to build SQL layer with Apache Calcite because > 1. It has done the hard job of parsing, translating logical plan to physical > plan and optimizing. > 2. It is under active development and has a great community. > 3. It's proved to be a good solution since Apache Storm, Apache Flink and > Apache Samza all build their Streaming SQL with Apache Calcite > Note SQL here actually means Streaming SQL dialects supported by Calcite > (check reference 1 and 2). Please checkout reference 3 for an example > implementation. > The physical plan will be translated to Gearpump high level DSL. > References: > 1. http://www.slideshare.net/julianhyde/streaming-sql > 2. https://calcite.apache.org/docs/stream.html > 3. https://github.com/milinda/samza-sql -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (GEARPUMP-346) No script to start new worker or new master to join in the cluster
[ https://issues.apache.org/jira/browse/GEARPUMP-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manu Zhang updated GEARPUMP-346: Summary: No script to start new worker or new master to join in the cluster (was: Not script to start new worker or new master to join in the cluster) > No script to start new worker or new master to join in the cluster > -- > > Key: GEARPUMP-346 > URL: https://issues.apache.org/jira/browse/GEARPUMP-346 > Project: Apache Gearpump > Issue Type: Wish >Reporter: Xuetong Zhu >Priority: Minor > > First,start a cluster by start-cluster.sh,then I want start a new worker join > in the cluster, but not found appropriate script. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (GEARPUMP-346) Not script to start new worker or new master to join in the cluster
[ https://issues.apache.org/jira/browse/GEARPUMP-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xuetong Zhu updated GEARPUMP-346: - Summary: Not script to start new worker or new master to join in the cluster (was: not script to start new worker or new master to join in the cluster) > Not script to start new worker or new master to join in the cluster > --- > > Key: GEARPUMP-346 > URL: https://issues.apache.org/jira/browse/GEARPUMP-346 > Project: Apache Gearpump > Issue Type: Wish >Reporter: Xuetong Zhu >Priority: Minor > > First,start a cluster by start-cluster.sh,then I want start a new worker join > in the cluster, but not found appropriate script. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (GEARPUMP-346) not script to start new worker or new master to join in the cluster
Xuetong Zhu created GEARPUMP-346: Summary: not script to start new worker or new master to join in the cluster Key: GEARPUMP-346 URL: https://issues.apache.org/jira/browse/GEARPUMP-346 Project: Apache Gearpump Issue Type: Wish Reporter: Xuetong Zhu Priority: Minor First,start a cluster by start-cluster.sh,then I want start a new worker join in the cluster, but not found appropriate script. -- This message was sent by Atlassian JIRA (v6.4.14#64029)