Bad error reporting when changing schema
See original GitHub issueInitial schema is kinda:
module default {
type Ticket {
required property title -> str;
}
}
And the new schema is:
module default {
abstract type Something {
property kind -> str;
}
type Ticket extending Something {
required property title -> str;
}
}
I’m not sure if this update makes sense, but the error definitely don’t:
InternalServerError: 'kind'
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
How do I resolve issues with missing or incorrect schema ...
If the value is missing or wrong then it likely means that other things were not done properly to the database and it...
Read more >Common DB schema change mistakes | Database Lab
Observing schema mismatch errors such as those above may lead to the "give ... some application schema, this approach is usually a bad...
Read more >Understanding schema errors
The schema is defined by the XSD. Schema errors occur where there is a problem with the structure or order of the file,...
Read more >Error handling - Apollo GraphQL Docs
The request was parsed successfully and is valid against the server's schema, but the server couldn't resolve which operation to run.
Read more >Compaction Exception after schema change
Symptom. After drop a column from the table schema, compaction fails with the exception in the system.log and debug.log. ERROR [ ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I can reproduce. Will have a fix soon.
This ix fixed.