# Avro序列化失败，SchemaRegistryException：不兼容的schema版本

- **ID:** `data/avro-schema-registry-serialization-version-mismatch`
- **领域:** data
- **类别:** schema_error
- **错误码:** `SchemaRegistryException`
- **验证级别:** ai_generated
- **修复率:** 82%

## 根因

Confluent Schema Registry强制执行兼容性规则（BACKWARD、FORWARD、FULL），并拒绝违反配置策略的schema演进，通常因为删除字段或更改类型导致破坏现有消费者。

## 版本兼容性

| 版本 | 状态 | 引入 | 弃用 |
|------|------|------|------|
| Confluent Platform 7.5 | active | — | — |
| Confluent Platform 7.6 | active | — | — |
| Apache Kafka 3.5 | active | — | — |
| Apache Kafka 3.6 | active | — | — |

## 解决方案

1. ```
   Temporarily set compatibility to BACKWARD_TRANSITIVE for the subject, register the new schema, then revert to original policy: `curl -X PUT -H 'Content-Type: application/vnd.schemaregistry.v1+json' -d '{"compatibility": "BACKWARD_TRANSITIVE"}' https://registry:8081/config/subject-name`
   ```
2. ```
   Add the new field with a default value to maintain backward compatibility: `{"name": "new_field", "type": "string", "default": ""}`
   ```
3. ```
   Use FULL_TRANSITIVE compatibility and register a new version that adds fields with defaults and removes no fields
   ```

## 无效尝试

- **** — Schema Registry does not allow deletion of schemas that have been used; you must use soft delete or wait for the cleanup policy. (85% 失败率)
- **** — This creates a new subject that existing consumers are not subscribed to, breaking data flow and requiring manual topic reconfiguration. (70% 失败率)
- **** — Disabling compatibility entirely allows any schema change, which can silently break downstream consumers and cause production incidents. (60% 失败率)