D. Ferruzzi
D. Ferruzzi
These are old system tests that are not AIP-47 compliant and are either already replaced or are in the process of being replaced by correct ones. I don't se any...
A recent PR pointed out this "trick" and I figure we can clean up the embedded code snippets by moving test-specific operator parameters out of the START/END blocks so the...
Adds hooks, operators, sensors, triggers, and waiters to enable support for Amazon Bedrock Knowledge Bases. This includes Bedrock Data Sources and Ingestion Jobs, and some light additions (a thin hook,...
### What happened? When OTel support was added, it enabled adding tags to metrics. Metrics such as `ti.start..` became `ti.start` with the tags for `dag_id` and `task_id`. Statsd does not...
The Bedrock team recently implemented a restriction against internal teams creating no-commitment throughput in order to reserve that capacity for public users. That change causes this test to fail with...
Both of these calls are super fast and neither has any kind of waiter or means of checking the status, so here can not be any sensor or trigger for...
### Apache Airflow version 2.6.2 ### What happened There is an issue with the `airflow_ti.start...` and `airflow_ti.finish...` metrics when running Airflow with OpenTelemetry. Both of those get emitted when run...
### Apache Airflow version 2.6.2 ### What happened The timers `airflow_dagrun..first_task_scheduling_delay` and `airflow_dagrun.schedule_delay.` both get emitted correctly in StatsD but not in OTel. I am submitting this as an Issue...
### Apache Airflow version 2.6.2 ### What happened It is my understanding that the `airflow_local_task_*` metric is only called when the task is explicitly called using airflow cli command, locally....
### Apache Airflow version 2.6.2 ### What happened The counter `sla_missed` gets emitted in StatsD but not in Otel. I am submitting this as an Issue since I will be...