What Is New in Jedis 3.5
Jedis 3.5 delivers a significant update focused on modern Redis features and enhanced API stability. This release introduces support for new Redis commands and refines the client's internal architecture for better reliability.
| Category | Key Changes |
|---|---|
| New Features | Support for ACL, ZPOPMIN, ZPOPMAX, and other Redis commands. |
| Improvements | Refactored internal connection handling, better pipeline management. |
| Bug Fixes | Resolved issues with connection leaks and protocol parsing. |
| Deprecated | Legacy methods and constructors marked for future removal. |
Which new Redis commands are now supported?
Jedis 3.5 adds full support for several important Redis commands. This includes ACL (Access Control List) operations for managing user permissions, which is critical for production security setups.
The blocking commands ZPOPMIN and ZPOPMAX are now implemented, providing better ways to handle sorted set operations. You'll also find support for other commands that were previously missing, closing the gap between Jedis and the latest Redis server capabilities.
How has connection handling been improved?
The internal connection handling received a major refactor to prevent resource leaks. This matters because connection leaks were a common pain point in long-running applications, leading to instability.
Pipeline execution has been made more robust, ensuring that all commands are properly sent and responses are correctly read. The changes make the client more predictable under heavy load, which is exactly what you need for production systems.
What breaking changes should I watch for?
Several deprecated methods and constructors are now officially removed. If you've been ignoring deprecation warnings, your code might break when upgrading.
The API cleanup removes legacy cruft, making the client cleaner and easier to maintain. In practice, you should run your test suite and check for any calls to methods that were marked as deprecated in earlier versions.
FAQ
Does Jedis 3.5 require a specific Redis server version?
No, but to use the new commands like ACL, you need a Redis server that supports them (v6.0+ for ACL). The client itself remains compatible with older servers.
Are there any performance improvements in this release?
Yes, the connection handling refactor reduces overhead and prevents leaks, which can improve performance and stability in applications with high connection churn.
How do I use the new ACL functionality?
You can now call methods like aclSetUser(), aclGetUser(), and aclDelUser() directly on your Jedis instance to manage access control lists programmatically.
Is it safe to upgrade from Jedis 3.4?
Generally yes, but check for uses of deprecated methods that were removed. The changes are mostly additive, but the removed deprecated APIs could cause compile errors.
What was the main driver for the connection handling changes?
The goal was to fix elusive connection leak bugs that occurred in certain edge cases, making the client more reliable for long-running services and frameworks.