Last checked and updated on 10 Jun 2026
What Is New in Jedis 6.1
Jedis 6.1 delivers a focused set of enhancements that improve the developer experience and add support for newer Redis commands. This release is about refinement and keeping pace with the evolving Redis ecosystem.
| Category | Key Changes |
|---|---|
| New Features | Support for ACL commands, JSON commands, and other new Redis features. |
| Improvements | Enhanced connection handling, URI validation, and method overloads. |
| Bug Fixes | Resolved issues with connection exceptions and command execution. |
| Deprecated | Marked older methods for future removal. |
What new Redis commands are supported?
Jedis 6.1 expands its command coverage to include several important additions from recent Redis versions. This keeps your Java applications in sync with the full power of your Redis server.
The release adds support for ACL (ACL WHOAMI, ACL LIST), JSON (JSON.SET, JSON.GET), and other commands like ZDIFF, ZINTER, ZUNION, and LMOVE. You can now use these directly without resorting to the generic sendCommand() method.
How is connection management improved?
Connection handling is more robust in this version. The changes prevent edge cases that could lead to resource leaks or unclear error messages.
Specifically, the JedisPooled constructor now properly closes connections if an exception occurs during initialization. The JedisSharding class also got an update to validate input URIs, catching configuration errors earlier. These are the small touches that make the client more reliable in production.
What methods have been deprecated?
A few older methods have been marked for removal in future versions. This is a standard cleanup process to streamline the API.
The deprecated methods include setDataSource() and the old zrangeByScore() overloads that used double parameters. You should migrate to the newer alternatives that use ZRangeParams and similar modern constructs for better consistency.
Were any critical bugs fixed?
Yes, a couple of important bugs were squashed. These fixes address issues that could surface during connection failures or specific command usage.
One fix ensures a JedisDataException is properly thrown when a connection is broken. Another resolves a problem where the CLIENT TRACKINGINFO command wasn't working correctly with the JedisCluster class. These patches improve overall stability.
FAQ
Does Jedis 6.1 add support for Redis JSON?
Yes, it does. You can now use commands like JSON.SET and JSON.GET directly through the Jedis API, making it easier to work with JSON documents stored in Redis.
I use ACLs on my Redis server. Is there better support now?
Absolutely. This release introduces support for ACL commands such as ACL WHOAMI and ACL LIST, allowing you to manage and check authentication controls from your Java code.
What should I use instead of the deprecated zrangeByScore methods?
You should transition to using the zrangeByScore() methods that accept ZRangeParams objects. This offers a more flexible and type-safe way to define your range queries.
Were there any fixes for connection pools?
Yes. The JedisPooled class was improved to ensure connections are properly closed if an exception happens during the pool's initialization phase, preventing potential leaks.
Is the LMOVE command available in JedisCluster?
Yes, support for the LMOVE command has been added, enabling you to atomically move elements between lists in a cluster environment.