| name | Schema Evolution Manager |
| description | Manages schema evolution and compatibility across data systems |
| version | 1.0.0 |
| category | Data Governance |
| skillId | SK-DEA-011 |
| allowed-tools | ["Read","Write","Edit","Glob","Grep","Bash"] |
| graph | {"domains":["domain:data-engineering"],"specializations":["specialization:data-engineering-analytics"],"skillAreas":["skill-area:schema-evolution","skill-area:data-governance"],"roles":["role:data-engineer","role:analytics-engineer"],"workflows":["workflow:data-pipeline-deployment"],"topics":["topic:data-mesh"]} |
Schema Evolution Manager
Overview
Manages schema evolution and compatibility across data systems. This skill ensures safe schema changes that maintain backward and forward compatibility.
Capabilities
- Schema compatibility checking (Avro, Protobuf, JSON Schema)
- Breaking change detection
- Migration script generation
- Version management
- Schema registry operations
- Backward/forward compatibility validation
- Schema documentation generation
- Cross-system schema synchronization
Input Schema
{
"currentSchema": "object",
"proposedSchema": "object",
"schemaFormat": "avro|protobuf|jsonschema|ddl",
"compatibilityMode": "backward|forward|full|none"
}
Output Schema
{
"compatible": "boolean",
"breakingChanges": ["object"],
"migrationScript": "string",
"recommendations": ["string"],
"versionInfo": "object"
}
Target Processes
- Streaming Pipeline
- ETL/ELT Pipeline
- Data Catalog
- Pipeline Migration
Usage Guidelines
- Provide current and proposed schema definitions
- Specify schema format for proper parsing
- Define compatibility mode based on system requirements
- Review breaking changes before proceeding with migration
Best Practices
- Always test schema changes in non-production first
- Use schema registry for centralized schema management
- Document schema versions and changes
- Plan migration strategies for breaking changes
- Coordinate schema changes across dependent systems