Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracking Issue: Towards a more redis-compatible database #1942

Open
21 of 24 tasks
PragmaTwice opened this issue Dec 18, 2023 · 3 comments · Fixed by #2244
Open
21 of 24 tasks

Tracking Issue: Towards a more redis-compatible database #1942

PragmaTwice opened this issue Dec 18, 2023 · 3 comments · Fixed by #2244
Labels

Comments

@PragmaTwice
Copy link
Member

PragmaTwice commented Dec 18, 2023

In order to be more compatible with redis, here are commands that exist in Redis (excluding Redis Stack) but are not supported in Kvrocks:

We very much welcome anyone to claim the tasks and start to contribute to Kvrocks. If you need any help during the contribution process, you can leave a message under the corresponding issue.

Also, the parts of existing commands that are incompatible with redis are worthy of attention and welcome any contribution.

It succeed #595.

@PragmaTwice PragmaTwice changed the title Towards a more redis-compatible database Tracking Issue: Towards a more redis-compatible database Dec 18, 2023
@tisonkun
Copy link
Member

Test suite in other client impl can help.

We writes C++ unit tests and Golang cases with redis-go. IIRC redis-go runs regression tests for Kvrocks also.

I tried Redisson but still have some troubles - #1912

Perhaps also other clients in https://redis.io/resources/clients/

@PragmaTwice PragmaTwice pinned this issue Dec 18, 2023
@jihuayu
Copy link
Member

jihuayu commented Jan 3, 2024

We can add support for BITOPS command BIT/BYTE option

@git-hulk
Copy link
Member

git-hulk commented Jan 3, 2024

@jihuayu done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Development

Successfully merging a pull request may close this issue.

4 participants