https://github.com/elek/docker-livy
Dockerized Livy, REST server for Apache Spark
https://github.com/elek/docker-livy
Last synced: 10 months ago
JSON representation
Dockerized Livy, REST server for Apache Spark
- Host: GitHub
- URL: https://github.com/elek/docker-livy
- Owner: elek
- License: apache-2.0
- Created: 2016-12-21T18:09:21.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2018-02-26T01:05:34.000Z (over 8 years ago)
- Last Synced: 2025-04-13T16:09:54.392Z (about 1 year ago)
- Language: Shell
- Size: 4.88 KB
- Stars: 2
- Watchers: 1
- Forks: 3
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Livy docker image
These images are part of the bigdata docker image series. All of the images use the same [base docker image](https://github.com/elek/docker-bigdata-base) which contains advanced configuration loading. For more detailed instruction see the [README](https://github.com/elek/docker-bigdata-base/blob/master/README.md) in the docker-bigdata-base repository.
## Configuration
The image could be configured:
* With environment variables
* With the key value store of the consul server
* With Spring config server
For examples and more details see the [repository](https://github.com/elek/docker-bigdata-base) of the base image.
## Running
Using the image depends from the configuration loading and the exact use case. You can find multiple examples in [this](https://github.com/elek/bigdata-docker) repository to use the images:
* on the local machine using docker-compose
* on remote cluster using ansible
* on remote cluster and local macine with using docker-compose downloaded from the consul image.
### Smoketest
```
docker run --net=host -it elek/livy
curl localhost:8998/sessions -X POST --data '{"kind":"spark"}' -H "Content-Type: application/json"
curl localhost:8998/sessions
curl localhost:8998/sessions/0/statements -X POST -H 'Content-Type: application/json' -d '{"code":"print(\"asd\")"}'
curl localhost:8998/sessions/0/statements/0
```
## Versioning policy
The latest tag points to the latest configuration loading and the latest stable version.
If there is plain version tag without prefix it is synchronized with the version of the original software.
It there is a prefix (eg. HDP) it includes a specific version from a specific distribution.
As the configuration loading in the base image is constantly evolving even the tags of older releases may be refreshed over the time.
**As livy currently only supports spark 1.6 the latest version is based on the latest stable 1.6.**