From the source code, I notice that the 512m limitation check of string keys is only applied to append and setrange command. Neither the set nor the setnx do che check.
And by config the client-query-buffer-limit and proto-max-bulk-len to a size larger than 512m, say 1024mb, I successfully inserted 1GB bytes into a string key.
So is it a bug or just an intended design? Should I rely this feature in my work?