Tracking issue for dependency redis-protocol
#2
Comments
J0HN50N133
added a commit
that referenced
this issue
Apr 11, 2024
* feat: add commands crate * fix: ut log level should at least 'debug' * chore(deps): vendor redis-protocol to my own fork as describe in #2 * feat: add commands parser framework * chore(deps): use redis-protocol 5.0.1 * refactor: database hold borrow directly instead of Arc to avoid overhead * refactor: use serde to deserialize config type instead of builder * feat: add execution process of set command * feat: read configuration file * feat: support parse ttl * refactor: clean the implementation of Set::execute * test: support test in ramdisk
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, in
redis-protocol, if you enablecodecand disableresp2,resp2will still be enabled sincecodecimpliesresp2. However, there is no reason to enable this if I've already disabledresp2. Currently, use theredis-protocolof my own fork.The text was updated successfully, but these errors were encountered: