Area: Product Issues
Sub-Area: Metadata Tests
Issue
Metadata tests configured with "set_domain" actions in the failing section correctly identify assets that meet the test criteria but do not actually assign the specified domain to those assets. The test runs successfully and reports the expected number of failing assets, but the domain assignment action fails to execute, leaving the assets without the intended domain assignment.
You Might Be Asking
- Why is my metadata test showing failed assets but not applying the domain?
- Is my metadata test configuration incorrect for domain assignment?
- Why does the test execute but the set_domain action doesn't work?
Solution
This issue was caused by a bug in DataHub Cloud versions prior to v1.0.2 where metadata test actions could be missed during async execution. The bug has been fixed and the solution depends on your DataHub version:
-
Check your DataHub Cloud version:
- Navigate to your DataHub instance settings or contact your administrator
- Verify if you're running DataHub Cloud v1.0.2 or later
-
If running v1.0.1 or earlier:
- Request an upgrade to v1.0.2 or later from your DataHub support team
- The fix was included in the v1.0.2-cloud release
-
If already on v1.0.2 or later:
- Verify that metadata tests are enabled in your deployment
- Check that
METADATA_TESTS_ENABLED=truein your configuration - Ensure the test is active and not disabled in the UI
-
Verify your metadata test configuration:
on: types: - dataset - dashboard - chart conditions: or: - property: dataPlatformInstance.platform operator: equals values: - 'urn:li:dataPlatform:' rules: and: - property: domains.domains operator: exists actions: passing: [] failing: - type: set_domain values: - 'urn:li:domain: ' -
Test the fix:
- Run your metadata test again after the upgrade
- Verify that domains are actually assigned to the failing assets
- Check the domain assignment in the DataHub UI
Additional Notes
This was a confirmed product bug that affected the async execution of metadata test actions specifically for domain assignment. The issue was tracked and resolved in DataHub Cloud v1.0.2. If you continue to experience issues after upgrading to v1.0.2 or later, this may indicate a different underlying problem that should be escalated to DataHub support. As a temporary workaround while waiting for the fix, you can manually assign domains using the UI, GraphQL API, or bulk operations.
Related Documentation
Tags: metadata-tests, domain-assignment, set-domain, product-bug, cloud-version, test-actions, async-execution, configuration, domain-management, failing-actions