Upgrade or remove lineage
Upgrade
- Unzip the new bundle into a new folder and copy your
.envinto it. - Run
./init-env.shin the new folder: it adds any setting the new version requires and leaves yours alone. Compare with the new.env.examplefor new optional settings. - From the old folder:
docker compose -f docker-compose-lineage.yml down(without-v, so the lineage stays). - From the new folder:
docker compose -f docker-compose-lineage.yml up -d. Marquez migrates its database on start.
The Hop side needs nothing unless the release notes say so.
Stop a Hop installation from sending lineage
./install-lineage.sh --hop-home /path/to/hop --disable
or set HOP_LINEAGE_ENABLED=N in the container's environment. The other settings stay, so
switching back on is the same command without --disable.
Remove the bundle
docker compose -f docker-compose-lineage.yml down # keeps the lineage
docker compose -f docker-compose-lineage.yml down -v # also deletes it
Switch lineage off on the Hop side first, or every run logs that it cannot reach Marquez.