[GitHub] zeppelin pull request #3051: Fix a broken link in the landing page
Github user asfgit closed the pull request at: https://github.com/apache/zeppelin/pull/3051 ---
[GitHub] zeppelin issue #3051: Fix a broken link in the landing page
Github user Leemoonsoo commented on the issue: https://github.com/apache/zeppelin/pull/3051 Thanks @Byeol for contribution! Merge this as a hotfix. ---
[GitHub] zeppelin pull request #3051: Fix a broken link in the landing page
GitHub user Byeol opened a pull request: https://github.com/apache/zeppelin/pull/3051 Fix a broken link in the landing page ### What is this PR for? Fix a broken link in the landing page ### What type of PR is it? Documentation ### What is the Jira issue? * Open an issue on Jira https://issues.apache.org/jira/browse/ZEPPELIN/ * Put link here, and add [ZEPPELIN-*Jira number*] in PR title, eg. [ZEPPELIN-533] ### How should this be tested? * First time? Setup Travis CI as described on https://zeppelin.apache.org/contribution/contributions.html#continuous-integration * Strongly recommended: add automated unit tests for any new or changed behavior * Outline any manual steps to test the PR here. ### Screenshots (if appropriate) ### Questions: * Does the licenses files need update? No * Is there breaking changes for older versions? No * Does this needs documentation? No You can merge this pull request into a Git repository by running: $ git pull https://github.com/Byeol/zeppelin fix-broken-link Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/3051.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 #3051 commit b1f33cc1034448f69d3ba30d4144f35ef08a2f4a Author: Jaewon Seo Date: 2018-07-04T05:30:00Z Fix a broken link in the landing page ---
[GitHub] zeppelin issue #3049: [ZEPPELIN-3580]
Github user Leemoonsoo commented on the issue: https://github.com/apache/zeppelin/pull/3049 Thanks @oxygen311 for the contribution. Could you resolve conflict and see if it passes CI? ---
[GitHub] zeppelin issue #3050: ZEPPELIN-3581. Add "type": "textarea" to "default.stat...
Github user Leemoonsoo commented on the issue: https://github.com/apache/zeppelin/pull/3050 LGTM ---
[GitHub] zeppelin pull request #3050: ZEPPELIN-3581. Add "type": "textarea" to "defau...
GitHub user mebelousov opened a pull request: https://github.com/apache/zeppelin/pull/3050 ZEPPELIN-3581. Add "type": "textarea" to "default.statementPrecode" in interpreter-setting.json ### What is this PR for? Fix "interpreter-setting.json" for JDBC interpreter ### What type of PR is it? Bug Fix ### What is the Jira issue? [ZEPPELIN-3581](https://issues.apache.org/jira/browse/ZEPPELIN-3581) ### How should this be tested? * Check text area near the "default.statementPrecode" setting. ### Questions: * Does the licenses files need update? no * Is there breaking changes for older versions? no * Does this needs documentation? no You can merge this pull request into a Git repository by running: $ git pull https://github.com/TinkoffCreditSystems/zeppelin ZEPPELIN-3581 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/3050.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 #3050 commit 4b052ed6b88d77d1cbb6b5e3754c1fe9a7615e58 Author: Maxim Belousov Date: 2018-07-03T17:20:22Z Add "type": "textarea" to "default.statementPrecode" ---
[jira] [Created] (ZEPPELIN-3581) Add type of "default.statementPrecode" in JDBC interpreter-setting.json
Maxim Belousov created ZEPPELIN-3581: Summary: Add type of "default.statementPrecode" in JDBC interpreter-setting.json Key: ZEPPELIN-3581 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3581 Project: Zeppelin Issue Type: Bug Reporter: Maxim Belousov Assignee: Maxim Belousov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
Re: Docker build error
Thanks Jeff. It's working now. Any idea why it was failing though? On Mon, Jul 2, 2018 at 10:59 PM Jeff Zhang wrote: > I have published the Docker for 0.8.0, feel free to try again. > > > > Chaoran Yu 于2018年7月3日周二 上午1:51写道： > > > This is also blocking my adoption of 0.8.0. I filed a JIRA ticket for it: > > https://issues.apache.org/jira/browse/ZEPPELIN-3571 > > > > > > On Mon, Jul 2, 2018 at 1:16 PM Andrea Santurbano > > wrote: > > > > > Dear group, > > > I'm trying to pull the latest Zeppelin's build from Docker, but I > recive > > an > > > error message. Looking through the docker hub page ( > > > https://hub.docker.com/r/apache/zeppelin/builds/) I see a lot of > errors > > > related to the version 0.8. > > > Is it possibile to fix this? > > > Thanks > > > Andrea > > > > > >
[GitHub] zeppelin issue #3048: [Docs] Update java version to 1.8
Github user zjffdu commented on the issue: https://github.com/apache/zeppelin/pull/3048 Update jdk in `yarn_install.md` ---
[GitHub] zeppelin pull request #3049: [ZEPPELIN-3580]
GitHub user oxygen311 opened a pull request: https://github.com/apache/zeppelin/pull/3049 [ZEPPELIN-3580] ### What is this PR for? Adds rename note method to rest api ### What type of PR is it? Improvement ### What is the Jira issue? issue on Jira: https://issues.apache.org/jira/browse/ZEPPELIN-3580 You can merge this pull request into a Git repository by running: $ git pull https://github.com/TinkoffCreditSystems/zeppelin ZEPPELIN-3585 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/3049.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 #3049 commit ad880ed31d6158a5cdcecfff7759d3a03c644bb0 Author: oxygen311 Date: 2018-07-02T16:31:09Z Add rename method to rest api commit 4df7c6dbaee5c3702f8da6d21cd981a5a17c557d Author: oxygen311 Date: 2018-07-03T12:07:23Z Add rename method to rest api ---
[GitHub] zeppelin pull request #3048: [Docs] Update java version to 1.8
GitHub user mebelousov opened a pull request: https://github.com/apache/zeppelin/pull/3048 [Docs] Update java version to 1.8 ### What is this PR for? This continues https://github.com/apache/zeppelin/pull/3029 (ZEPPELIN-621 - Bump Java version to Java 8) ### What type of PR is it? Bug Fix ### Questions: * Does the licenses files need update? no * Is there breaking changes for older versions? no * Does this needs documentation? no You can merge this pull request into a Git repository by running: $ git pull https://github.com/TinkoffCreditSystems/zeppelin java1.8doc Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/3048.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 #3048 commit 877dcbbe81139b373d2998895469f27b414f74b6 Author: Maxim Belousov Date: 2018-07-03T10:33:34Z Update java version to 1.8 in docs This continues https://github.com/apache/zeppelin/pull/3029 ---
[jira] [Created] (ZEPPELIN-3580) Add rename function in rest api
Alexey created ZEPPELIN-3580: Summary: Add rename function in rest api Key: ZEPPELIN-3580 URL: https://issues.apache.org/jira/browse/ZEPPELIN-3580 Project: Zeppelin Issue Type: Improvement Reporter: Alexey -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] zeppelin issue #3035: [ZEPPELIN-3553] Fix URLs on "Multi-user Support" page
Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/3035 looks like we should port to branch-0.8 too ---
[GitHub] zeppelin issue #3015: [ZEPPELIN-3490] Yarn cluster mode doesn't work with de...
Github user jongyoul commented on the issue: https://github.com/apache/zeppelin/pull/3015 Oh... missed. Will fix it. ---
[GitHub] zeppelin issue #3035: [ZEPPELIN-3553] Fix URLs on "Multi-user Support" page
Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/3035 merging if no more comment ---
[GitHub] zeppelin issue #3015: [ZEPPELIN-3490] Yarn cluster mode doesn't work with de...
Github user felixcheung commented on the issue: https://github.com/apache/zeppelin/pull/3015 how about this https://github.com/apache/zeppelin/pull/3015#discussion_r194955050 and https://github.com/apache/zeppelin/pull/3015#discussion_r194955106? ---
