Elgato_dark/OpenMetadata
1
0
Fork 0
mirror of https://github.com/open-metadata/OpenMetadata synced 2026-05-24 09:39:11 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 5
OpenMetadata/bootstrap/sql/migrations/native/1.13.0/mysql
History
Sriharsha Chintalapani 4bb6574815
Some checks are pending
Integration Tests - MySQL + Elasticsearch / Detect Changes (push) Waiting to run
Details
Integration Tests - MySQL + Elasticsearch / integration-tests-mysql-elasticsearch (push) Blocked by required conditions
Details
Integration Tests - PostgreSQL + Elasticsearch + Redis / Detect Changes (push) Waiting to run
Details
Integration Tests - PostgreSQL + Elasticsearch + Redis / integration-tests-postgres-elasticsearch-redis (push) Blocked by required conditions
Details
Integration Tests - PostgreSQL + OpenSearch / Detect Changes (push) Waiting to run
Details
Integration Tests - PostgreSQL + OpenSearch / integration-tests-postgres-opensearch (push) Blocked by required conditions
Details
Java Checkstyle / java-checkstyle (push) Waiting to run
Details
Maven Collate Tests / maven-collate-ci (push) Waiting to run
Details
OpenMetadata Service Unit Tests / Detect Changes (push) Waiting to run
Details
OpenMetadata Service Unit Tests / openmetadata-service-unit-tests (push) Blocked by required conditions
Details
OpenMetadata Service Unit Tests / k8s_operator-unit-tests (push) Blocked by required conditions
Details
OpenMetadata Service Unit Tests / openmetadata-service-unit-tests-status (push) Blocked by required conditions
Details
Publish Package to Maven Central Repository / publish-maven-packages (push) Waiting to run
Details
fix(glossary): preserve all relation types between same term pair (#28172) 
* fix(glossary): preserve all relation types between same term pair

The entity_relationship primary key (fromId, toId, relation) caused the
second INSERT for the same (term, term) pair to UPSERT and overwrite the
json discriminator, silently dropping any previously stored relationType.
Adding the same target term with "synonym" then "seeAlso" left only one
relation visible on GET.

Extend the PK to (fromId, toId, relation, relationType) so each typed
relation lives in its own row. The new column defaults to '' for every
non-glossary edge, leaving existing call sites and queries semantically
unchanged. CollectionDAO.deleteWithRelationType and countByRelationType
now filter on the column directly instead of JSON_EXTRACT. The 1.13.0
schemaChanges migration backfills relationType from the existing json
for glossaryTerm RELATED_TO rows, then atomically swaps the PK.

Adds three integration tests in GlossaryTermResourceIT covering the
add path, the targeted-removal path, and tag-usage cleanup when a
table tagged with a glossary term is hard-deleted.
2026-05-16 11:37:21 -07:00
..
postDataMigrationSQLScript.sql Add migrations to ensure PII are really enabled (#27921) 2026-05-08 15:39:29 +00:00
schemaChanges.sql fix(glossary): preserve all relation types between same term pair (#28172) 2026-05-16 11:37:21 -07:00