tree: a9bc02ed90935609f001029c0700b1c386045de7 [path history] [tgz]
  1. bin/
  2. examples/
  3. .dockerignore
  4. Dockerfile
  5. README.md
  6. requirements-db.txt
docker/images/pinot-superset/README.md

Superset

Docker image for Superset with Pinot integration.

How to build

Below command will build docker image and tag it as apachepinot/pinot-superset:0.36.0.

You can also build directly with docker build command by setting arguments:

docker build --build-arg SUPERSET_VERSION=0.36.0 --tag apachepinot/pinot-superset:0.36.0 .

How to push

docker push apachepinot/pinot-superset:0.36.0

Configuration

Follow the instructions provided by Apache Superset for writing your own superset_config.py.

Place this file in a local directory and mount this directory to /etc/superset inside the container. This location is included in the image's PYTHONPATH. Mounting this file to a different location is possible, but it will need to be in the PYTHONPATH.

Volumes

The image defines two data volumes: one for mounting configuration into the container, and one for data (logs, SQLite DBs, &c).

The configuration volume is located alternatively at /etc/superset or /app/superset; either is acceptable. Both of these directories are included in the PYTHONPATH of the image. Mount any configuration (specifically the superset_config.py file) here to have it read by the app on startup.

The data volume is located at /app/superset_home and it is where you would mount your SQLite file (if you are using that as your backend), or a volume to collect any logs that are routed there.

Kubernetes Examples

Please refer to superset.yaml as k8s deployment example.