Anything that was new in Redis 7 is not currently in KeyDB. This is a decent list of features I found that would be impacted.
https://www.instaclustr.com/blog/redis-7-new-features/ KeyDB has it on their roadmap to merge in the latest features from Redis 7 but that's not complete yet (nor can I find any published status on that). EPEL doesn't currently provide Redis for 8/9 because it got pulled in directly by RH. RHEL 9 does have a module for redis 7 but the default is 6, so that's easy at least. There should be no problems with adding KeyDB to EPEL 8/9 - in fact it doesn't even conflict with redis (though keydb-devel will conflict with redis-devel as keydb-devel still uses identical names of some libraries it produces). Honestly trying to replace redis with KeyDB in Fedora would be a step backwards and cause headaches so I don't think it's feasible, at least until redis v7 features are merged into KeyDB. On Thu, Mar 21, 2024 at 1:05 PM Scott Williams <vwfoxg...@gmail.com> wrote: > Assuming KeyDB gets accepted (it looks close from the Bugzilla review), we > should obsolete redis for KeyDB in Fedora 40+ and consider eventually doing > likewise with EPEL as well, since we aren't going to be able to ship any > redis patches moving forward. I feel less strongly about that for EPEL as > for Fedora. As a Fedora redis user, personally, having KeyDB in-place > replace redis on upgrade to Fedora 40 seems like the best possible route > moving forward to limit end-user disruption and technical debt for Fedora. > > As long as KeyDB's multi-threading isn't enabled out of box, it should > essentially be equivalent to redis-6 as I understand it. We're currently > shipping redis-7.2.4 in Fedora 39. Are there any potential redis-7 > specific compatibility problems with KeyDB migration? > -- > _______________________________________________ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- Jonathan Wright AlmaLinux Foundation Mattermost: chat <https://chat.almalinux.org/almalinux/messages/@jonathan>
-- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
