The reason this is true, is because it’s redundant to have separate support for them, when you can just as easily do base 64 encoding and store them as strings. It’s not clear what more do we need to provide on top.
Badger has a limit that the key+value size shouldn’t exceed the size of a single value log. We don’t support a value spilling across file boundaries; which is the reason why the total size should be below that. You could set the value log size to a higher limit, and then send out larger values (say 4GB), it’s all configurable.
There’s nothing inherent to Dgraph, which would slow a binary blob’s retrieval, or affect its performance. Under the surface, Badger is dealing with this, and it can deal with these in a much more efficient manner than other KV DBs.