forked from apache/incubator-livy
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
With this change Livy will only build and run with JDK8. While this doesn't necessarily preclude using Java 7 for running Spark itself, that is not encouraged due to possible issues with serialization. There are a few small changes elsewhere that I made so tests would pass, but aren't related to the java 8 change: - a small tweak to the fallback code that initializes the python interpreter, which was failing with a weird reflection error. - expose the user's home directory in the MiniYarnCluster, to allow the tests to see pip packages installed in the user's home. - tweak the python API tests so that the pytest cache does not pollute the source directory. - changed Travis to use Oracle's JDK, since the Open JDK path was mixing Java 8 and 9 and causing errors. - updated jacoco to latest stable. Author: Marcelo Vanzin <[email protected]> Closes apache#111 from vanzin/LIVY-510.
- Loading branch information
Showing
8 changed files
with
34 additions
and
95 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters