mirror of
https://github.com/open-metadata/OpenMetadata
synced 2026-05-24 09:39:11 +00:00
733921f510
* Fix: align glossary term relation type colors with design system System-defined relation types (relatedTo, synonym, antonym, etc.) were initialized with old Ant Design palette colors (#1890ff, #722ed1, …) while the frontend RELATION_META constants had been updated to the new design system colors (#1570ef, #b42318, …). Because renderColorBadge used record.color (from the backend) unconditionally, the stale Ant Design colors were always displayed instead of the intended ones. - Frontend: renderColorBadge now treats RELATION_META as authoritative for system-defined types so the correct design-system color is always shown, regardless of what color value is stored in the backend. - Backend (SettingsCache.java): default colors updated for new installs. - DB migration (2.0.0): postDataMigrationSQLScript added for MySQL and PostgreSQL to update colors in existing deployments without touching user-added custom relation types. - Tests: unit tests for renderColorBadge color-resolution logic; integration test asserting all ten system-defined types return the expected hex values from the API. Fixes #openmetadata/OpenMetadata * Remove dev-only MySQL 2.0.0 migration script * Remove dev-only PostgreSQL 2.0.0 migration script * Fix: align glossary term relation settings colors and remove duplicate 1.13.0 migration; Remove glossary term relation migrations mistakenly re-added in 1.13.0 and update relation type colors in the 1.14.0 migration INSERT to use design system tokens instead of old Ant Design colors. * fix lint * add more test * address feedback * fix prettier formatting in test file Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * remove GlossaryTermRelationSettings test file from branch Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
40 lines
No EOL
1.6 KiB
SQL
40 lines
No EOL
1.6 KiB
SQL
UPDATE ingestion_pipeline_entity
|
|
SET json = (json::jsonb #- '{sourceConfig,config,computeMetrics}')::json
|
|
WHERE json::jsonb -> 'sourceConfig' -> 'config' -> 'computeMetrics' IS NOT NULL
|
|
AND pipelineType = 'profiler';
|
|
|
|
-- Hard-delete ingestion pipelines for Iceberg services (must run before service migration)
|
|
DELETE FROM ingestion_pipeline_entity ipe
|
|
USING dbservice_entity dse
|
|
WHERE dse.serviceType = 'Iceberg'
|
|
AND ipe.json::jsonb -> 'service' ->> 'type' = 'databaseService'
|
|
AND ipe.json::jsonb -> 'service' ->> 'id' = dse.id;
|
|
|
|
-- Migrate Iceberg database services to CustomDatabase (connector removed)
|
|
-- serviceType is a GENERATED column derived from json, so only update json
|
|
UPDATE dbservice_entity
|
|
SET json = jsonb_set(
|
|
jsonb_set(
|
|
json::jsonb,
|
|
'{serviceType}', '"CustomDatabase"'
|
|
),
|
|
'{connection,config,type}', '"CustomDatabase"'
|
|
)::json
|
|
WHERE serviceType = 'Iceberg';
|
|
|
|
-- Migrate serviceType in child entities (serviceType is in JSON blob only, no generated column)
|
|
UPDATE database_entity
|
|
SET json = jsonb_set(json::jsonb, '{serviceType}', '"CustomDatabase"')::json
|
|
WHERE json->>'serviceType' = 'Iceberg';
|
|
|
|
UPDATE database_schema_entity
|
|
SET json = jsonb_set(json::jsonb, '{serviceType}', '"CustomDatabase"')::json
|
|
WHERE json->>'serviceType' = 'Iceberg';
|
|
|
|
UPDATE table_entity
|
|
SET json = jsonb_set(json::jsonb, '{serviceType}', '"CustomDatabase"')::json
|
|
WHERE json->>'serviceType' = 'Iceberg';
|
|
|
|
UPDATE stored_procedure_entity
|
|
SET json = jsonb_set(json::jsonb, '{serviceType}', '"CustomDatabase"')::json
|
|
WHERE json->>'serviceType' = 'Iceberg'; |