Affected module
Ingestion Framework (Profiler) — MariaDB metrics computation
⸻
Describe the bug
When running the profiler against a MariaDB table, the profiling workflow fails during metric computation. Specifically, the median metric calculation throws a runtime exception indicating a mismatch in the function signature for MariaDBMedian._compute_sqa_fn().
The error occurs during window metric computation in the MariaDB profiler interface and causes the entire profiling job to fail.
Error message:
TypeError: MariaDBMedian._compute_sqa_fn() takes 4 positional arguments but 5 were given
RuntimeError: MariaDBMedian._compute_sqa_fn() takes 4 positional arguments but 5 were given
This appears to be related to the median metric implementation for MariaDB in the profiler.
⸻
To Reproduce
1. Configure a MariaDB database service in OpenMetadata
2. Enable table profiling
3. Run the ingestion/profiler workflow (e.g., via Airflow)
4. The profiler fails during metric computation
Stack trace excerpt:
File ".../profiler_interface.py", line 74, in _compute_window_metrics
[metric(column).fn() for metric in metrics]
File ".../metrics/window/median.py", line 87, in fn
return self._compute_sqa_fn()
TypeError: MariaDBMedian._compute_sqa_fn() takes 4 positional arguments but 5 were given
⸻
Expected behavior
The profiler should compute metrics (including median) successfully for MariaDB tables without raising an exception, and the profiling workflow should complete normally.
⸻
Version:
• OS: Linux
• Python version: default by docker image
• OpenMetadata version: 1.12.1
• OpenMetadata Ingestion package version: openmetadata-ingestion==1.12.1
• Database: MariaDB
• Profiler execution environment: Airflow
⸻
Additional context
• The issue occurs specifically when profiling tables in MariaDB
• The failure happens during metric computation, likely related to the median window metric
• No custom metrics are configured
• The error originates from:
metadata/profiler/metrics/window/median.py
metadata/profiler/interface/sqlalchemy/mariadb/profiler_interface.py
Potential root cause hypothesis:
• Function signature mismatch introduced in a recent version
• Incompatibility between OpenMetadata server version and ingestion package version
• Bug in MariaDB-specific median metric implementation
Affected module
Ingestion Framework (Profiler) — MariaDB metrics computation
⸻
Describe the bug
When running the profiler against a MariaDB table, the profiling workflow fails during metric computation. Specifically, the median metric calculation throws a runtime exception indicating a mismatch in the function signature for MariaDBMedian._compute_sqa_fn().
The error occurs during window metric computation in the MariaDB profiler interface and causes the entire profiling job to fail.
Error message:
TypeError: MariaDBMedian._compute_sqa_fn() takes 4 positional arguments but 5 were given
RuntimeError: MariaDBMedian._compute_sqa_fn() takes 4 positional arguments but 5 were given
This appears to be related to the median metric implementation for MariaDB in the profiler.
⸻
To Reproduce
1. Configure a MariaDB database service in OpenMetadata
2. Enable table profiling
3. Run the ingestion/profiler workflow (e.g., via Airflow)
4. The profiler fails during metric computation
Stack trace excerpt:
⸻
Expected behavior
The profiler should compute metrics (including median) successfully for MariaDB tables without raising an exception, and the profiling workflow should complete normally.
⸻
Version:
• OS: Linux
• Python version: default by docker image
• OpenMetadata version: 1.12.1
• OpenMetadata Ingestion package version: openmetadata-ingestion==1.12.1
• Database: MariaDB
• Profiler execution environment: Airflow
⸻
Additional context
• The issue occurs specifically when profiling tables in MariaDB
• The failure happens during metric computation, likely related to the median window metric
• No custom metrics are configured
• The error originates from:
metadata/profiler/metrics/window/median.py
metadata/profiler/interface/sqlalchemy/mariadb/profiler_interface.py
Potential root cause hypothesis:
• Function signature mismatch introduced in a recent version
• Incompatibility between OpenMetadata server version and ingestion package version
• Bug in MariaDB-specific median metric implementation