Metadata Test Conditions UI Bug for Structured Properties – DataHub Customer Support Portal

Area: Product Issues

Sub-Area: Metadata Tests UI

Issue

When building Metadata Test conditions in the DataHub UI, selecting the "Exists" or "Does not exist" operator for a Structured Property incorrectly leaves the "Select a value..." input field visible. This creates an inconsistency with standard metadata fields (like Owners) where the value input correctly disappears for existence checks, since these operators only verify property presence rather than specific values.

You Might Be Asking

Why does the value field still appear when I select "Exists" for a structured property?
Is this affecting my metadata test evaluation?
How does this differ from other property types in the condition builder?

Solution

This was a confirmed UI bug that has been resolved in DataHub Cloud version v1.0.0-cloud. The issue was caused by missing operator validation in the structured property condition builder code.

For Current Users: Upgrade to DataHub Cloud v1.0.0-cloud or later where this issue is fixed
Verification: After upgrading, create a new Metadata Test and verify that selecting "Exists" or "Does not exist" for structured properties now properly hides the value input field
Existing Tests: No action needed - your existing metadata tests continue to evaluate correctly as the "Exists" operator ignores any values in the input field

Additional Notes

This was a cosmetic UI bug only and did not affect the functionality of metadata tests. Tests using the "Exists" operator on structured properties evaluated correctly even when the value field was visible. The bug existed since structured properties were first introduced to Metadata Tests and was an original implementation oversight rather than a regression. The fix ensures consistent behavior across all property types in the condition builder interface.

Issue

You Might Be Asking

Solution

Additional Notes

Related Documentation