Ontology Validation for Semantic Metadata Changes in Upgrades
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data management systems face challenges in maintaining metadata integrity during rolling upgrades, leading to metadata corruption due to developers' failure to update label handlers, which can impact customer experience and user experience with subtle problems detected with delays.
Innovation Solution
Implementing an ontology specification with read and write ontologies to validate metadata changes, ensuring compatibility across different database versions by flagging errors if updates are not made, thereby preventing metadata corruption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If developers do not update label handlers during rolling upgrades, then deployment speed is improved, but metadata integrity deteriorates leading to corruption
Solution Approach 1:
The system performs preliminary validation by comparing the new metadata schema against the old schema before applying updates. This preliminary check identifies semantic changes that would corrupt metadata, allowing the system to prevent corruption while maintaining deployment efficiency through automated validation rather than requiring manual label handler updates.
Solution Approach 2:
The system implements feedback mechanisms by monitoring metadata schema changes during rolling upgrades and providing validation results. When semantic changes are detected, the system feedbacks error information to prevent deployment, ensuring metadata integrity is maintained without requiring developers to manually update label handlers.
2Reliability
If manual validation of metadata changes is performed, then metadata integrity is improved, but time consumption increases
Solution Approach 1:
The system performs self-validation by automatically comparing metadata schemas and detecting semantic changes without requiring manual intervention. The validation process is embedded in the deployment workflow, allowing the system to validate metadata integrity automatically and efficiently without consuming additional time.
Solution Approach 2:
The validation process is performed preliminarily as part of the deployment preparation phase, not as a separate manual step. This preliminary automated validation identifies potential corruption issues before deployment, eliminating the need for time-consuming manual validation after deployment.
3Productivity
If semantic changes are allowed without validation, then deployment efficiency is improved, but metadata corruption risk increases
Solution Approach 1:
The system applies preliminary anti-action by detecting semantic changes that would cause metadata corruption and blocking them before deployment. The validation mechanism identifies harmful schema changes in advance and prevents them from being applied, eliminating metadata corruption risk while maintaining deployment efficiency through automated prevention.
Solution Approach 2:
The system provides feedback when semantic changes are detected that would corrupt metadata, preventing deployment of harmful changes. This feedback mechanism allows the system to maintain high deployment efficiency by automatically filtering out corrupting changes without requiring manual review of every change.
Data Source
AI summary
Methods, systems, and devices for data management are described. A data management system may generate, at a first time, an ontology defining a structure and one or more relationships between one or more columns across a set of tables included in a database of a data management system. In some examples, the data management system may receive, at a second time that is later than the first time, an input to access at least one column of the one or more columns of the database in the data management system, where accessing the at least one column may correspond to a semantic change to the metadata of the database. The data management system may determine whether the ontology is updated to reflect the semantic change to the metadata of the database. The data management system may then generate a validation result based on determining whether the ontology is updated.