Repository navigation
Startup load accepts non-UTF-8 key names that SET and RESTORE refuse #446
Description
A key named bad:\xff\xfe, fetched from Valkey with valkey-cli --rdb and loaded with --preload-file, loads with no warning, and DBSIZE counts it. But SET or RESTORE of the same name answers ERR key must be valid UTF-8. So the server holds a key that clients can't recreate.
Fix: one rule everywhere. #437, binary-safe keys, accepts such keys everywhere and will resolve this; this issue tracks it until then.
Found while testing the migration guides (kividb.io/docs/migrate) against KiviDB 1.2.0, on Linux x86_64 release builds.
Activity
Keys as bytes everywhere the keyspace is read back
Keys, stream names and vector-set elements of any bytes (#437, step 3)