#33485·OpenMetadata

Profiler logs ModuleNotFoundError warning per-table for dialects without a system metrics implementation (e.g. Vertica)

Author: jnrimjhimCreated Sep 17, 2026Updated Sep 18, 2026
Labelsbugprofiler

Affected module

Data Quality / Profiler

Describe the bug

When running a Profiler Workflow against a dialect that has no system-metrics implementation (e.g. Vertica), the following is logged for every table processed, even though profiling itself succeeds and is unaffected:

ModuleNotFoundError: No module named 'metadata.profiler.metrics.system.vertica' [2026-09-04 08:47:47] WARNING {metadata.Profiler:system:161} - No implementation found for vertica

To Reproduce

  1. Set up a Profiler Workflow against a data source dialect that has no system-metrics implementation (e.g. Vertica).
  2. Set loggerLevel: DEBUG in the workflow config.
  3. Run the workflow with Python 3.11 on version 1.12.4.
  4. Observe the logs — for every table processed, the following is emitted:
ModuleNotFoundError: No module named 'metadata.profiler.metrics.system.vertica'
WARNING {metadata.Profiler:system:161} - No implementation found for vertica
  1. Note that profiling results and DQ tests complete successfully and are unaffected — only the log noise is the issue.

Expected behavior

The "no implementation found" warning (and the underlying failed import) should be logged once per dialect per run, not once per table.

OS

No response

Python version

No response

OpenMetadata version

2.0.1

OpenMetadata Ingestion package version

No response

Additional context

No response

Pre-submission checklist

  • I searched for duplicate issues.
  • I removed credentials, hostnames, emails, and other sensitive data from logs and config.

Source: open-metadata/OpenMetadata