Wow, thanks for getting to the bottom of this.
Wow, this is incredibly dangerous. I wonder if we should be disabling DROP this in Slash GraphQL until this is fixed, as restore(backup(cluster)) != cluster.
I have a dumb question, but don’t we stream the drop operation into the WAL, and therefore won’t it go into the backup? Or is this handled differently in dgraph? From the description, it feels almost like DROP is bypassing dgraph and going straight to badger or something?