evita-schema-change

To add a new field to an evitaDB schema while maintaining backward compatibility, follow an eight-layer recipe that propagates changes across contracts, DTOs, builders, mutations, external APIs, Kryo serializers, WAL serializers, and validation.

The eight-layer pattern for evitaDB schema mutations is a comprehensive recipe covering contracts, DTOs, builders, mutations, external APIs (gRPC/GraphQL/REST), Kryo serializers, WAL serializers, and thorough validation to ensure safe schema changes.

To propagate evitaDB schema changes across gRPC, GraphQL, and REST APIs, apply the schema change recipe that systematically updates external API layers alongside contracts, DTOs, and mutations to preserve consistency.

Yes, you can safely extend ReferenceSchema, EntitySchema, or AttributeSchema with a new configuration option by applying the end-to-end schema change recipe across all eight layers, including serializers and validation.

Updating both Kryo and WAL serializers during evitaDB schema changes is required to ensure data persistence and write-ahead logging correctly recognize the mutated schema structures without breaking existing serialized data.

Modifying evitaDB schema types requires touching all eight layers simultaneously; skipping validation or serializer updates in any layer will break data consistency or backward compatibility across gRPC, GraphQL, and REST APIs.