Is there any alternative?
Hum, I see that flag in v20.11.0
Dgraph version : v20.11.0
Dgraph codename : tchalla
Dgraph SHA-256 : 8591d39e46caf64c1f8b9d8c8dcdb1afe7a61bbe5d9e08cd597faa4978717544
Commit SHA-1 : c4245ad55
Commit timestamp : 2020-12-16 15:55:40 +0530
Branch : HEAD
Go version : go1.15.5
jemalloc enabled : false
dgraph alpha -h | grep mutation
--abort_older_than string Abort any pending transactions older than this duration. The liveness of a transaction is determined by its last mutation. (default "5m")
--mutations string Set mutation mode to allow, disallow, or strict. (default "allow")
--mutations_nquad_limit uint Limit for the maximum number of nquads that can be inserted in a mutation request (default 1000000)
--pending_proposals int Number of pending mutation proposals. Useful for rate limiting. (default 256)
Hi, @MichelDiz
I found these two commits, fix(Dgraph): Switch command line options to kebab-case (#6908) and fix(Dgraph): Revert to snake case flags (#7087), but in the source code in 20.07.3 tag, neither mutations_nquad_limit nor mutations-nquad-limit can be found. I don’t know when it was deleted.
There are problems with simple queries in v20.11.0. I don’t want to use it for the moment. 
I see it there(in both links provided), there was no removal. It was probably some formatting process.
But, why do you miss it? is there any shipped binary missing this flag?
Thank you for your reply, @MichelDiz.
I just used the official image of version 20.07.3, and I can see that the source code here has no mutations_nquad_limit flag.
As you can see, this flag was introduced 3 months ago feat(mutations): Introducte mutatoinsNquadLimit by ashish-goswami · Pull Request #6561 · dgraph-io/dgraph · GitHub - so it wasn’t backported to 20.07.x - It feels like it is part of 20.11.x only. @hardik/@dmai can confirm.
If you are using the latest docs or master, you can bump into some unsupported docs for your version.
If you have found it in some 20.07.3 tag, it was in some rc1. And it should not be there. Cuz this PR 6561 is from October and 20.07.X is from July. Also, I don’t see any backport PR, have to do a deeper look if so. Or wait for Hardik to confirm.
Also, Daniel and Hardik can tell if we could do a backport to 20.07.3.
@Valdanito can you share where in 20.07 did you see that flag? We did not implement it on 20.07 so it should not be there in an version of 20.07.
Also can you elaborate on what you mean by “There are problems with simple queries in v20.11.0.” comment? We would be happy to investigate that further.
Sorry, it seems to be my fault. I will ask questions about v20.11.0 in a new post.