Bigeye Airflow Operators for Airflow Versions 1.10.15
Operators
Create Metric Operator (bigeye_airflow.oerators.create_metric_operator)
The CreateMetricOperator creates metrics from a list of metric configurations provided to the operator. This operator will fill in reasonable defaults like setting thresholds. It authenticates through an Airflow connection ID and offers the option to run the metrics after those metrics have been created. Please review the link below to understand the structure of the configurations.
Create or Update Metric Swagger
Parameters
- connection_id: str - The Airfow connection ID used to store the required Bigeye credential.
- warehouse_id: int - The Bigeye source/warehouse id to which the metric configurations will be deployed.
- configuration: List[dict] - A list of metric configurations conforming to the following schema.
schema_name: str table_name: str column_name: str metric_template_id: uuid.UUID metric_name: str notifications: List[str] thresholds: List[dict] filters: List[str] group_by: List[str] user_defined_metric_name: str metric_type: SimpleMetricCategory default_check_frequency_hours: int update_schedule: str delay_at_update: str timezone: str should_backfill: bool lookback_type: str lookback_days: int window_size: str _window_size_seconds - run_after_upsert: bool - If true it will run the metrics after creation. Defaults to False.
Run Metrics Operator
The RunMetricsOperator will run metrics in Bigeye based on the following:
- All metrics for a given table, by providing warehouse ID, schema name and table name.
- Any and all metrics, given a list of metric IDs.
Currently, if a list of metric IDs is provided these will be run instead of metrics provided for warehouse_id, schema_name, table_name.
Parameters
- connection_id: str - The Airfow connection ID used to store the required Bigeye credential.
- warehouse_id: int - The Bigeye source/warehouse id for which metrics will be run.
- schema_name: str - The schema name for which metrics will be run.
- table_name: str - The table name for which metrics will be run.
- metric_ids: List[int] - The metric ids to run.
Metadata
Release files for bigeye-airflow1 0.0.28
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| bigeye_airflow1-0.0.28-py3-none-any.whl | Python 3 | none | any | Details |
Release files / bigeye_airflow1-0.0.28-py3-none-any.whl
| Download URL | bigeye_airflow1-0.0.28-py3-none-any.whl |
|---|---|
| Size | 12.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
75850d3e7ccaa251d72f29e2a03104190533aeedac216c276cbf07bff152af38
|
|
BLAKE2b-256 checksum How to use checksums |
a915f7178e00c19c170d1ad46a344cc7121e6a401a87d5bc7e35b431fcd95549
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.10.9
|
Security for bigeye-airflow1 0.0.28
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.