Dgraph Release 21.03 ( Resilient Rocket ) is available. As part of the 21.03.0 release we have introduced many improvements and major new features. Following sections provides information about what has been implemented as part of the release.
New Features
Enterprise
Audit Logs
Multi Tenancy
Learner Nodes (Read Replicas)
Change Data Capture
Dgraph
Single manifest for Backups
Vault for ACL secrets
Flags Consolidation
Loading files from S3/minio
Leadership Metrics
Transaction Metrics
Support multiple JWK URLs
GraphQL authorization using standard claim
Apollo Federation
GraphQL Upserts
Custom DQL Subscription
Multiple Unique ids
Cascade with Pagination
IN Filter for different data type
Customer DQL with groupby
Authorization: Bearer {token}
Lambda(Web) hooks for add/update/delete mutations
Subscription websocket with gzip
@id with type Int
Support for has filter on list of fields
Improvements and Fixes
Dgraph
JSON parsing for GraphQL
Simdjson improvements
SinceTS improvement
Backup manifest file consolidation
And many more performance and stability improvements. Details of which can be found in changelogs
Discontinued Features
Dgraph
Schema Versioning and History
Ratel Binary from the Dgraph Release Package
Known Bugs and Issues
Dgraph
Ludicrous mode issues ( We have noticed ludicrous mode is a bit unstable when coming to few corner use cases, we are working on it to fix them quickly )
Important Notes
Upgrade to 21.03 from existing instances of Dgraph can be done using Backup/Restore or Export/Import features in Dgraph. Please refer to this page : Upgrades
“Flag consolidation” improvement has significantly changed the way Dgraph flags are configured. You can find useful information on this page : Super Flags
We were trying to store GraphQL schema history within Dgraph. It was complex and largely unused. So, we decided to remove that. Typically, schema versioning is something users would handle on their own.
If Dgraph Cloud users ask for this, this feature can be achieved from within the Cloud infrastructure.
I agree better versioned in the clients control. The backups have the schema though so restoring a backup would also include the schema at that point in time. #removeComplexity#makeRoomForBiggerThingsToCome
Forgot to add that Ratel was removed everywhere. Why? What the real reason?
It was not production but testing\debugging ready tool. Now it’s complicated to run itself in all deployments and containers. Now it’s make fast-start work with dgraph more complicated
Hello @1Const1 , we wanted to simplify the Dgraph package and only group needed binaries in the release.
For the purpose of your usecase there are few ways you can still use Ratel easily
Leverage https://play.dgraph.io/ which contains all the latest features in Ratel needed for 21.03.
I would think new instances would be one of the first things they do since upgrading is a different process… I’m sure they’ve been concentrating on the upgrade process.