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

abhimanyusinghgaur (Abhimanyu Singh Gaur) October 9, 2020, 6:57am 10

Yes

Not in GraphQL. But, I think this is what happens when someone does a {"drop_attr": "pred_name"} on /alter endpoint. I guess, Slash has a use-case for that scenario. @akashjain971 can provide better details.

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