This release is a pre-release and may not be stable for production use.
floe-lineage-marquez
Marquez lineage backend plugin for floe - OpenLineage reference implementation for data lineage.
Overview
This plugin provides a MarquezLineageBackendPlugin that configures OpenLineage HTTP transport to send lineage events to a Marquez deployment. This is recommended for:
- Self-hosted data lineage tracking
- OpenLineage reference implementation
- Integration with existing Marquez infrastructure
Installation
pip install floe-lineage-marquez
Usage
Via manifest.yaml (Recommended)
# manifest.yaml
plugins:
lineage_backend: marquez
Programmatic Usage
from floe_lineage_marquez import MarquezLineageBackendPlugin
plugin = MarquezLineageBackendPlugin(
url="https://marquez:5000",
api_key="optional-api-key" # pragma: allowlist secret
)
# Plugin will be loaded automatically by LineageProvider
Configuration
The Marquez plugin configures OpenLineage HTTP transport:
- Default endpoint:
marquez:5000(HTTPS) - Protocol: HTTPS/REST (HTTP for localhost development only)
- API endpoint:
/api/v1/lineage
For production, configure:
url: Marquez API base URL (use HTTPS)api_key: Optional authentication
Security
HTTPS Enforcement: By default, only HTTPS URLs are accepted (except for localhost).
HTTP is allowed for localhost, 127.0.0.1, and ::1 for local development.
Development Override: To use HTTP with non-localhost URLs in development environments:
export FLOE_ALLOW_INSECURE_HTTP=true
Warning: Never use this in production. The plugin logs a CRITICAL warning when this override is active.
PostgreSQL Credentials: The get_helm_values() method uses Kubernetes Secrets via Bitnami's existingSecret pattern. Create a secret before deploying:
# Create the required Kubernetes secret
kubectl create secret generic marquez-postgresql-credentials \
--from-literal=postgres-password='<your-admin-password>' \
--from-literal=password='<your-user-password>'
Helm Deployment
The plugin provides Helm values for self-hosted deployment:
plugin = MarquezLineageBackendPlugin()
helm_values = plugin.get_helm_values()
# Returns Marquez + PostgreSQL chart values
Requirements
- Python 3.10+
- floe-core >= 0.1.0
Related
- Marquez - OpenLineage reference implementation
- OpenLineage - Open standard for data lineage
License
Apache-2.0
Metadata
Release files for floe-lineage-marquez 0.1.0a1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| floe_lineage_marquez-0.1.0a1.tar.gz | 14.3 kB | Without provenance | Details for floe_lineage_marquez-0.1.0a1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| floe_lineage_marquez-0.1.0a1-py3-none-any.whl | Python 3 | none | any | Details for floe_lineage_marquez-0.1.0a1-py3-none-any.whl |
Total release size: 23.8 kB
Release files / floe_lineage_marquez-0.1.0a1.tar.gz
| Download URL | floe_lineage_marquez-0.1.0a1.tar.gz |
|---|---|
| Size | 14.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
222c45ace83ce37a9f3484a66e2a579bc6d708e54e4ce4d4e94897262ed1b39a
|
|
BLAKE2b-256 checksum How to use checksums |
079adae7f2371d3357ec183fd02c6527a27d66166f036b7da7f4e181458ac5b6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Release files / floe_lineage_marquez-0.1.0a1-py3-none-any.whl
| Download URL | floe_lineage_marquez-0.1.0a1-py3-none-any.whl |
|---|---|
| Size | 9.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3b44f13a1243893437f08740aa7024a17034cde604f76c193e8e3f82ab29063b
|
|
BLAKE2b-256 checksum How to use checksums |
01575a41df3d27bd1ea5ea2084697e4c5c54f03f449134b0261d770823a7629c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Security for floe-lineage-marquez 0.1.0a1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.