Skip to main content

Lineage in the Putki stack

In the full Putki stack of a Professional or Enterprise edition, lineage is part of the stack. Its compose file starts Marquez, its database and the lineage UI, and switches lineage on for Putki Web, the Hop server and the scheduled jobs. You do not need the lineage bundle.

Set MARQUEZ_DB_PASSWORD in the stack's .env; the stack does not start without it.

  • The lineage UI listens on 127.0.0.1:3001 of the stack host, and the Marquez API on 127.0.0.1:5000. Inside the stack nothing needs a key: Hop reaches Marquez on the stack's own network. Neither has a login, so do not publish them as they are. To share the UI, put it behind a proxy with a login, or run the lineage bundle's proxy in front of it.
  • Scheduled jobs take the lineage settings from the stack when they are registered. After changing a HOP_LINEAGE_* setting, register them again: ./scripts/putki-compose.sh run --rm dkron-init.
  • The namespace is HOP_LINEAGE_OPENLINEAGE_NAMESPACE, putki unless you set it.