[GitHub] zeppelin issue #418: [DOCS] Zeppelin Flink Spark tutorial

Github user corneadoug commented on the issue: https://github.com/apache/zeppelin/pull/418 Awesome, Merging it --- 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] zeppelin issue #418: [DOCS] Zeppelin Flink Spark tutorial

Github user rawkintrevo commented on the issue: https://github.com/apache/zeppelin/pull/418 Yea I think I merged it or something. I fixed. --- 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] zeppelin issue #418: [DOCS] Zeppelin Flink Spark tutorial

Github user corneadoug commented on the issue: https://github.com/apache/zeppelin/pull/418 @rawkintrevo Did the rebase go wrong somehow? Seems there is a lot of commits that are not related to this PR --- If your project is set up for it, you can reply to this email and have your rep

[GitHub] zeppelin issue #418: [DOCS] Zeppelin Flink Spark tutorial

Github user rawkintrevo commented on the issue: https://github.com/apache/zeppelin/pull/418 @corneadoug done and 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 an

[GitHub] zeppelin issue #418: [DOCS] Zeppelin Flink Spark tutorial

Github user corneadoug commented on the issue: https://github.com/apache/zeppelin/pull/418 @rawkintrevo Lets remove the `incubator` from URLs, rebase, then merge it --- 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] zeppelin issue #418: [DOCS] Zeppelin Flink Spark tutorial

Github user rawkintrevo commented on the issue: https://github.com/apache/zeppelin/pull/418 @bzz or whoever is in charge of this, failed on flakey test. Can we do a merge on this? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub

[GitHub] zeppelin issue #418: [DOCS] Zeppelin Flink Spark tutorial

Github user rawkintrevo commented on the issue: https://github.com/apache/zeppelin/pull/418 Yea, I had intentionally left in 'getting started' as it was an install tutorial, but I just moved it to the 'more section' per your comment. --- If your project is set up for it, you can rep

[GitHub] zeppelin issue #418: [DOCS] Zeppelin Flink Spark tutorial

Github user AhyoungRyu commented on the issue: https://github.com/apache/zeppelin/pull/418 @rawkintrevo Yeah thanks! But still the docs existed in `Getting Started` section. Can we move this docs below [this line](https://github.com/apache/zeppelin/blob/master/docs/_includes/themes/ze

[GitHub] zeppelin issue #418: [DOCS] Zeppelin Flink Spark tutorial

Github user rawkintrevo commented on the issue: https://github.com/apache/zeppelin/pull/418 Good eye @AhyoungRyu , the navigation made more sense in December, I didn't look at it again since the rebase. Thanks! --- If your project is set up for it, you can reply to this em

[GitHub] zeppelin issue #418: [DOCS] Zeppelin Flink Spark tutorial

Github user rawkintrevo commented on the issue: https://github.com/apache/zeppelin/pull/418 @bzz took advantage of the break in the action on 116 to finish this off. Should be GTG now. Updated to Flink 1.0, Maven 3.3.9, Spark 1.6. Also added some points on just using Spark/