Report a Dgraph Bug
What version of Dgraph are you using?
Dgraph Version
$ dgraph version
Dgraph version : v21.03.1
Dgraph codename : rocket-1
Dgraph SHA-256 : a00b73d583a720aa787171e43b4cb4dbbf75b38e522f66c9943ab2f0263007fe
Commit SHA-1 : ea1cb5f35
Commit timestamp : 2021-06-17 20:38:11 +0530
Branch : HEAD
Go version : go1.16.2
jemalloc enabled : true
For Dgraph official documentation, visit https://dgraph.io/docs.
For discussions about Dgraph , visit https://discuss.dgraph.io.
For fully-managed Dgraph Cloud , visit https://dgraph.io/cloud.
Licensed variously under the Apache Public License 2.0 and Dgraph Community License.
Copyright 2015-2021 Dgraph Labs, Inc.
Have you tried reproducing the issue with the latest release?
Yes
What is the hardware spec (RAM, OS)?
MacOS 16GB RAM
Steps to reproduce the issue (command/config used to run Dgraph).
Run this against the /admin API on dgraph/standalone:
mutation {
dropData(allDataAndSchema: true) {
response {
code
message
}
}
}
Expected behaviour and actual result.
I’d like to use the dropData(allDataAndSchema: true)
mutation to programmatically truncate the data in my local test instance of dgraph after I push a new schema, however this endpoint seems to only exist in slash graphql.
Being able to do this programmatically would be a nice boost to local productivity.