Came across the below example via a bug report filed by @akashjain971 . Essentially when you alter GraphQL schema via /alter endpoint, the corresponding types and fields are not kept in-sync. Example: Schema: type Test{ id: ID! name: String! marks: Int! } type Person{ name: String…

Possible bug in GraphQL layer in Dgraph when altering schema via /alter

martinmr (Martin Martinez Rivera) October 7, 2020, 10:10pm 3

Not a bug since types and schema were not designed to be in sync. Not sure if we want to add this as a feature. Dropping fields when they are shared across types might have unintended consequences.

Topic		Replies	Views
Schema change not allowed from scalar to uid or vice versa while there is data for pred Issues dgraph , status:accepted , kind:bug , area:schema , ticket:created	9	2393	January 4, 2022
Replacing types in GraphQL Schema: Show left over data Dgraph Cloud / Slash GraphQL status:accepted , kind:feature , ticket:created	7	716	July 28, 2020
Disallow DQL schema changes for predicates used in GraphQL schema Dgraph kind:enhancement , status:accepted , ticket:created	10	813	April 22, 2021
Selective drop data for a certain type Dgraph Cloud / Slash GraphQL status:accepted , kind:feature , ticket:created	9	1779	August 21, 2020
How to delete a schema type using json Documentation kind:question	3	46	December 11, 2024

Possible bug in GraphQL layer in Dgraph when altering schema via /alter

Related topics