v1.WriteSchema relationship sanity check should skip permissions #733
Labels
area/api v1
Affects the v1 API
area/perf
Affects performance or scalability
priority/1 high
This is the top priority
To ensure that data remains valid across schema migrations,
v1.WriteSchema
performs a sanity check.An optimization that is missing for this sanity check is to skip permissions as they are computed and cannot contain any data themselves. This optimization would vastly improve the performance of large schema writes on production systems and make schema migrations that only modify permissions nearly instantaneous.
Big thanks to @williamdclt for the report the surfaced this issue.
The text was updated successfully, but these errors were encountered: