prefect-openmetadata
Welcome!
Using Prefect and OpenMetadata together will help you build and maintain a data platform you can trust.
Prefect allows you to coordinate your dataflow and provides visibility into the health of your workflow execution and workflow lineage. With OpenMetadata integration, you can enrich your orchestration system with metadata about data lineage, data catalog, data quality and governance, giving you more information about the health of your system.
Getting Started
Python setup
Requires an installation of Python 3.8+.
We recommend using a Python virtual environment manager such as pipenv, conda or virtualenv.
Installation
Install prefect-openmetadata with pip:
pip install prefect-openmetadata
Install OpenMetadata and Prefect
Head over to the install OpenMetadata page for detailed instructions on how to install and configure both platforms.
Write and run metadata ingestion flow
from prefect_openmetadata.flows import ingest_metadata
config = """See an example in the section: Run ingestion flow"""
if __name__ == "__main__":
ingest_metadata(config)
For more details, check the run ingestion flow section.
Schedule a metadata ingestion flow
Simple example:
prefect deployment build -a -n dev myflow.py:ingest_metadata --interval 900
For more details, check the schedule ingestion flow section.
Resources
If you encounter any bugs while using prefect-openmetadata, feel free to open an issue in the prefect-openmetadata repository.
If you have any questions or issues while using prefect-openmetadata, you can find help in either the Prefect Discourse forum or the Prefect Slack community.
Development
If you'd like to install a version of prefect-openmetadata for development, clone the repository and perform an editable install with pip:
git clone https://github.com/PrefectHQ/prefect-openmetadata.git
cd prefect-openmetadata/
pip install -e ".[dev]"
# Install linting pre-commit hooks
pre-commit install
Metadata
Release files for prefect-openmetadata 0.3.0
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 |
|---|---|---|---|---|
| prefect-openmetadata-0.3.0.tar.gz | 27.4 kB | Without provenance | Details for prefect-openmetadata-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| prefect_openmetadata-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for prefect_openmetadata-0.3.0-py3-none-any.whl |
Total release size: 37.9 kB
Release files / prefect-openmetadata-0.3.0.tar.gz
| Download URL | prefect-openmetadata-0.3.0.tar.gz |
|---|---|
| Size | 27.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5216eebd3bc24419f0131e5a944fbba2491940fc62b92b3e7843eda49bbcd576
|
|
BLAKE2b-256 checksum How to use checksums |
815436a03487acd566d72e7cc28066d7bb442571e6655903308a60d639f6839f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.6
|
Release files / prefect_openmetadata-0.3.0-py3-none-any.whl
| Download URL | prefect_openmetadata-0.3.0-py3-none-any.whl |
|---|---|
| Size | 10.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0173dc8f923923096f4b622a427d842f29e97b3cddb66098eee62cccd498a2c4
|
|
BLAKE2b-256 checksum How to use checksums |
109f8fd72ade6c6847a23fd2f47adcd9f05822607d850b2aabb1f564f2590c78
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.6
|
Security for prefect-openmetadata 0.3.0
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.