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

Question about redis cluster proxy roadmap #3

Closed
git-hulk opened this issue May 9, 2019 · 2 comments
Closed

Question about redis cluster proxy roadmap #3

git-hulk opened this issue May 9, 2019 · 2 comments

Comments

@git-hulk
Copy link
Contributor

git-hulk commented May 9, 2019

hey, @artix75

Would you mind publishing the roadmap of this project? And whether feature or bug fix PR is welcome now? I would be happy to accomplish some todo features if it's ok to issue the PR, like the query redirection.

Thanks~

@artix75
Copy link
Contributor

artix75 commented May 9, 2019

Hello @git-hulk, the project is still on its very early development stages. I've planned to give more info about it in the next weeks (as you can see, I still have to write a basic README :) ).
At the moment I'm concentrating all my efforts on strengthening the proxy's core functionalities (such as basic request routing, multiplexing handling, and so on).

So I don't known if I have much time for handling PRs right now, anyway any issue reporting is really welcomed.

As for future features, I can tell you that query redirection, multi-slot/multi-node queries and stateful/blocking queries are already planned to be supported.

For any question, I'll be very glad to answer :)

Thank you very much!

@git-hulk
Copy link
Contributor Author

git-hulk commented May 10, 2019

hi @artix75, Got it and thanks for your reply and great work, I would continue to follow the updates. If you need someone to do trivial work, I would be glad to do that. : )

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

No branches or pull requests

2 participants