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.
kamu: Register GeoSpark types at session startup
kamu: Register types after thriftserver creates a sub-session kamu: Updates for Spark 3 kamu: Update to latest Sedona kamu: Improve readme
- Loading branch information
Showing
6 changed files
with
51 additions
and
0 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
# Kamu fork of Apache Livy | ||
|
||
Kamu is building its own version of Livy for two reasons: | ||
- As of this time latest Livy release does not contain Slaca 2.12 binaries, which are needed for Spark 3+ compatibility | ||
- When working with Livy we want Apache Sedona types (GIS library) to be pre-registered inside the user's Spark session. Livy and Spark don't provide any hooks to do so, so we had to extend Livy to add them upon Spark session startup | ||
- **TODO:** We shoud investigate if the recently added `spark.sql.extensions` config option can allow such auto-registration | ||
|
||
## Building the fork | ||
|
||
First clone the repo and make sure you're on `kamu` branch. | ||
|
||
Build command: | ||
```sh | ||
mvn package -Pthriftserver -Pspark-3.0 -Pspark.version=3.0.0 -Pscala.version=2.12.13 -Pscala.binary.version=2.12 -DskipITs -DskipTests | ||
``` | ||
... this will take a while. | ||
|
||
Package will be produced under: | ||
|
||
```sh | ||
./assembly/target/apache-livy-{version}-kamu-bin.zip | ||
``` |
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