[GitHub] zeppelin issue #3029: ZEPPELIN-621 - Bump Java version to Java 8
Github user alexott commented on the issue: https://github.com/apache/zeppelin/pull/3029 Ok, it looks like it's working now, but really not sure what was wrong with configuration... ---
[GitHub] zeppelin issue #2997: Miscellaneous documentation fixes
Github user alexott commented on the issue: https://github.com/apache/zeppelin/pull/2997 Can we merge it into 0.8 branch because RC is cancelled? Should I send request against 0.8? ---
[GitHub] zeppelin issue #3029: ZEPPELIN-621 - Bump Java version to Java 8
Github user alexott commented on the issue: https://github.com/apache/zeppelin/pull/3029 @zjffdu I forgot to enable CI, and test is now running, although some tests are failed - will investigate over weekend... ---
[GitHub] zeppelin issue #3029: ZEPPELIN-621 - Bump Java version to Java 8
Github user alexott commented on the issue: https://github.com/apache/zeppelin/pull/3029 @jongyoul JDK is configured there as well, so I was going to change it everywhere, so people who develop using Vagrant, won't get problems... ---
[GitHub] zeppelin issue #2997: Miscellaneous documentation fixes
Github user alexott commented on the issue: https://github.com/apache/zeppelin/pull/2997 Done, thank you for review! ---
[GitHub] zeppelin pull request #3029: ZEPPELIN-621 - Bump Java version to Java 8
GitHub user alexott opened a pull request: https://github.com/apache/zeppelin/pull/3029 ZEPPELIN-621 - Bump Java version to Java 8 ### What is this PR for? This PR switches the project to use Java 8 - we already have dependency on Spark 2.2.0 that is Java 8+ only. ### What type of PR is it? Improvement ### What is the Jira issue? https://issues.apache.org/jira/browse/ZEPPELIN-621 You can merge this pull request into a Git repository by running: $ git pull https://github.com/alexott/zeppelin ZEPPELIN-621 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/3029.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 #3029 commit 07e80bb219e5a4b1e0da66920ef3b05d6c47 Author: Alex Ott Date: 2018-06-17T14:38:05Z bump Java to 1.8 commit 764bd341712e926ae326ae69058730b2cac87c5f Author: Alex Ott Date: 2018-06-18T18:15:23Z update Vagrant to 16.04 + Java 8 commit 51b9eccfba69c2c46d7a189cd8ce10a8c487a74d Author: Alex Ott Date: 2018-06-18T18:15:35Z Mention Java 8 as dependency ---
[GitHub] zeppelin issue #658: Switch to Java 8
Github user alexott commented on the issue: https://github.com/apache/zeppelin/pull/658 Why it still not implemented? Spark starting with 2.2.0 works only with Java 8... ---
[GitHub] zeppelin pull request #2997: Miscellaneous documentation fixes
GitHub user alexott opened a pull request: https://github.com/apache/zeppelin/pull/2997 Miscellaneous documentation fixes ### What is this PR for? This PR contains miscellaneous fixes & improvements for documentation: - fixes for code snippets formatting, like, https://zeppelin.apache.org/docs/0.8.0-SNAPSHOT/setup/security/shiro_authentication.html#apply-multiple-roles-in-shiro-configuration - fixes syntax highlighting (adding `scala`, `xml`, `java`, `bash`, ...) - fixes for list of interpreters - ... ### What type of PR is it? Documentation You can merge this pull request into a Git repository by running: $ git pull https://github.com/alexott/zeppelin doc-formatting-fixes Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/2997.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 #2997 commit a994f4ecf913129c37fd8cbabf7cfbb1264b8add Author: Alex Ott Date: 2018-06-01T09:42:19Z improve formatting for Cassandra interpreter docs commit c90b61f1114c32c529dc4c5665026e31975e0ba0 Author: Alex Ott Date: 2018-06-01T09:45:47Z use same capitalization in all interpreter names commit bb26a2954b6979808d90ef047a5fd376d05fa357 Author: Alex Ott Date: 2018-06-01T09:46:06Z use same formatting for parser name commit 5a7950e79c40b61d872be34000a561004eebe469 Author: Alex Ott Date: 2018-06-01T10:43:21Z add missing language spec for syntax highlighting commit 9d285a1b789c865c24de967731d8e05dfd32cca0 Author: Alex Ott Date: 2018-06-01T10:43:48Z Fix list of interpreters commit 63ca2b0e2823ddff9430ddfdd0f94cd922e3d56f Author: Alex Ott Date: 2018-06-01T10:45:26Z fix usage of the ``` markup that lead to broken formatting commit 37a2bb77888c13c04ed022283ee8e4f2394974d6 Author: Alex Ott Date: 2018-06-01T10:45:48Z miscellaneous fixes - wording, formatting, etc. ---
[GitHub] zeppelin issue #2959: ZEPPELIN-3443 - Fix regex to support optional space be...
Github user alexott commented on the issue: https://github.com/apache/zeppelin/pull/2959 Build failed because of problems of `urllib3`/`pyopenssl`... ---
[GitHub] zeppelin pull request #2959: ZEPPELIN-3443 - Fix regex to support optional s...
GitHub user alexott opened a pull request: https://github.com/apache/zeppelin/pull/2959 ZEPPELIN-3443 - Fix regex to support optional space before ; ### What is this PR for? Almost all regular expressions, except for DESCRIBE MATERIALIZED VIEW in the CQL interpreter allow to have an optional space before closing ; character. There is some code that uses these spaces before ; character, so the command fails when you copy/past commands. This PR fixes it ### What type of PR is it? Bug Fix ### What is the Jira issue? https://issues.apache.org/jira/browse/ZEPPELIN-3443 ### How should this be tested? Fix is trivial and doesn't require unit test, or extra testing You can merge this pull request into a Git repository by running: $ git pull https://github.com/alexott/zeppelin fix-mviews-regex Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zeppelin/pull/2959.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 #2959 commit 1efccc3efe3267c98def69afd28904f6d1c3e304 Author: Alex Ott <alex.ott@...> Date: 2018-05-04T12:23:19Z Fix regex to support optional space before ; ---
