Long data quality test names exceed database test name max length

[nickozilla]

Affected module
We are ingesting our dbt test metadata into OpenMetadata, and often see the following error in our external ingestion job

ERROR [2026-01-21 10:04:55,509] [dw-157 - PUT /api/v1/dataQuality/testDefinitions] o.o.s.r.d.TestDefinitionResource - Got exception: [UnableToExecuteStatementException] / message [org.postgresql.util.PSQLException: ERROR: value too long for type character varying(512)

This is because the way dbt generates test names is quite generous unless a custom test name is provided, it generates the test name as

• test name (not_null, unique, etc)
• model name (or source/seed/snapshot)
• column name (if relevant)
• arguments (if relevant, e.g. values for accepted_values)

https://docs.getdbt.com/reference/resource-properties/data-tests#custom-data-test-name

So all of our accepted_values dbt tests, and many other similar tests are failing ingestion due to their test name length.

The fixes are:

• Force all our dbt tests to make use of the custom test name
• Write a flyway to modify the column type to handle the potentially quite long default

Version:

• OS: Debian
• Python version: python:3.11-slim-bookworm
• OpenMetadata version: 1.11.5
• OpenMetadata Ingestion package version: openmetadata-ingestion[bigquery,postgres,dbt,looker,presidio-analyzer]==1.11.5.0

Additional context
Add any other context about the problem here.

[elenipatsiou-coll]

Thanks @nickozilla for opening this issue - really excited to get this fix into OpenMetadata 🙌

In the meantime, the easiest way to stay up to date is to ⭐ the OpenMetadata repo!

Also, you’re invited to our virtual community meetup this Wednesday! We’ll be sharing the OMD Q1 roadmap and hosting a community spotlight with real-world use cases from Wix. Hope you can join us!

[nickozilla]

Hi @elenipatsiou-coll - does this mean this is something that openmetadata sees this as worth fixing? If so I am happy to have a go at the PR myself

[nikhil255288]

Hi @elenipatsiou-coll — I'd like to work on this fix. I've located the Flyway migration path and plan to increase the column size for test names. I'll also check if the same constraint exists in MySQL migrations. Can you confirm the approach before I submit a PR?

[nikhil255288]

Hi @elenipatsiou-coll — I've submitted a fix in PR #27053. It increases the test_case.name column from varchar(256) to varchar(2048) with migration scripts for both MySQL and PostgreSQL. All CI checks are passing.