-
Notifications
You must be signed in to change notification settings - Fork 602
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[LIVY-457][REPL] Fix SQLContext is not initialized correctly issue #86
Conversation
Codecov Report
@@ Coverage Diff @@
## master #86 +/- ##
============================================
+ Coverage 71.43% 71.58% +0.14%
- Complexity 792 795 +3
============================================
Files 97 97
Lines 5399 5399
Branches 799 799
============================================
+ Hits 3857 3865 +8
+ Misses 1021 1012 -9
- Partials 521 522 +1
Continue to review full report at Codecov.
|
Ping @zjffdu @ajbozarth please help to review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Test again. |
Merging to master and branch 0.5. |
## What changes were proposed in this pull request? The signature of SQLContext's constructor is changed in Spark2, but we're still using the Spark1's signature, which will throw an exception when using this object. ## How was this patch tested? UT and local verification. Author: jerryshao <[email protected]> Closes #86 from jerryshao/LIVY-457. (cherry picked from commit cd8b112) Signed-off-by: jerryshao <[email protected]>
## What changes were proposed in this pull request? The signature of SQLContext's constructor is changed in Spark2, but we're still using the Spark1's signature, which will throw an exception when using this object. ## How was this patch tested? UT and local verification. Author: jerryshao <[email protected]> Closes apache#86 from jerryshao/LIVY-457. (cherry picked from commit cd8b112) Signed-off-by: jerryshao <[email protected]>
* [MINOR] Addressed Docs dependency security vulnerability followup Followup to 26428c5 Author: Alex Bozarth <[email protected]> Closes apache#82 from ajbozarth/gem. (cherry picked from commit 6d2ffdd) Signed-off-by: Alex Bozarth <[email protected]> * [MINOR] Fix travis builds Each individual commit has a more detailed description of what's being changed and why. At the moment, Travis builds don't work: * https://travis-ci.org/mineo/incubator-livy/builds/359324523 - the `sudo pip3 install --upgrade pip "setuptools < 36"` command fails with `sudo: pip3: command not found`. * fixing that, the `failing the org.apache.rat:apache-rat-plugin:0.12:check` maven goal fails because it sees `.pytest_cache` folders that it doesn't know about (pytest-dev/pytest#3286, failure in https://travis-ci.org/mineo/incubator-livy/jobs/359326261, check the raw log). This pull request works around the pip3 failures by just using pip as a callable module (possible since Python 3.4) and adding `.pytest_cache` to raw-excludes, as well as showing the contents of `rat.txt` files in the `after_failure` step. I concede that the pip change is more of a workaround, but I don't know how else to fix it and unblock testing. Running the tests on travis. Please review https://livy.incubator.apache.org/community/ before opening a pull request. Author: Wieland Hoffmann <[email protected]> Closes apache#84 from mineo/rat. (cherry picked from commit 06cfa7b) Signed-off-by: jerryshao <[email protected]> * [LIVY-455][REPL] Fix json4s doesn't support java.math.BigDecimal issue ## What changes were proposed in this pull request? Livy's SQLInterpreter will throw exception when rows contain java.math.BigDecimal data. This is because current version of json4s doesn't treat java.math.BigDecimal type as primitive type. On the contrary, json4s supports Scala BigDecimal as primitive type. So the fix is to convert java BigDecimal to Scala BigDecimal. ## How was this patch tested? Unit test is added. Author: jerryshao <[email protected]> Closes apache#85 from jerryshao/LIVY-455. (cherry picked from commit 7e4bb3b) Signed-off-by: jerryshao <[email protected]> * [LIVY-457][REPL] Fix SQLContext is not initialized correctly issue ## What changes were proposed in this pull request? The signature of SQLContext's constructor is changed in Spark2, but we're still using the Spark1's signature, which will throw an exception when using this object. ## How was this patch tested? UT and local verification. Author: jerryshao <[email protected]> Closes apache#86 from jerryshao/LIVY-457. (cherry picked from commit cd8b112) Signed-off-by: jerryshao <[email protected]> * [LIVY-466][RSC] Fix RSCDriver exception during RPC shutdown ## What changes were proposed in this pull request? During RSCDriver's shutdown, it will first shutdown RPC server, and then all the RPC clients. When RPC client is closed, it will register a timeout to avoid orphaned RSCDriver, but this is not necessary during RSCDriver's shutdown, so here fixing this issue. The details can be seen in [JIRA](https://issues.apache.org/jira/browse/LIVY-466). ## How was this patch tested? Local verification. Author: jerryshao <[email protected]> Closes apache#90 from jerryshao/LIVY-466. (cherry picked from commit e3f45a0) Signed-off-by: jerryshao <[email protected]> * [LIVY-472][SERVER] Improve the logs for fail-to-create session ## What changes were proposed in this pull request? Livy currently doesn't give a very clear log about the fail-to-create session, it only says that session related app tag cannot be found in RM, but doesn't tell user how to search and get the true root cause. So here change the logs to make it more clear. ## How was this patch tested? Local verification. Author: jerryshao <[email protected]> Closes apache#96 from jerryshao/LIVY-472. (cherry picked from commit ca4cad2) Signed-off-by: jerryshao <[email protected]> * [Security] Update to support pyspark and sparkr changes in Spark 2.3.1 * [LIVY-498][REPL] Fix Windows CRLF line ending issue in SparkR interpreter ## What changes were proposed in this pull request? If the issued query contains CRLF EOL, it will be failed to execute on *nix machine. This happens when submitting queries from Windows machine and executing on Linux machine. So here propose to convert statement to match system's EOL. ## How was this patch tested? New UT added. Author: jerryshao <[email protected]> Closes apache#105 from jerryshao/LIVY-498. (cherry picked from commit 8027ca7) Signed-off-by: jerryshao <[email protected]> * upgrade to work with spark 2.3.2
What changes were proposed in this pull request?
The signature of SQLContext's constructor is changed in Spark2, but we're still using the Spark1's signature, which will throw an exception when using this object.
How was this patch tested?
UT and local verification.