What Is New in Jedis 4.3
Jedis 4.3 brings a solid set of updates focused on new Redis commands, improved connection handling, and essential bug fixes. This release keeps the client aligned with the latest server capabilities while refining the developer experience.
| Category | Key Changes |
|---|---|
| New Features | Support for ACL commands, JSON commands, and other new Redis 6.2/7.0 features. |
| Improvements | Enhanced connection pool behavior and URI validation. |
| Bug Fixes | Resolved issues with cluster commands and connection management. |
| Deprecations | Marked older methods for removal in future versions. |
What new Redis commands are supported?
Jedis 4.3 adds support for several important command groups introduced in recent Redis versions. This includes commands for Access Control Lists (ACL) and the RedisJSON module.
You can now manage users and permissions directly through Jedis with commands like ACL SETUSER and
ACL GETUSER. For JSON operations, methods like json.set and json.get are
available, letting you work with JSON documents stored in Redis.
How is connection handling better?
The connection pool and URI handling have been made more robust. The changes prevent some edge-case connection leaks and improve the reliability of application shutdown.
In practice, this means your application is less likely to hold onto connections it doesn't need, which matters for long-running services. The validation for connection URIs is also stricter, helping you catch configuration errors early.
What bugs were squashed in this release?
This release addresses a handful of specific bugs that could trip up developers. One fix corrects the behavior of
the CLUSTER SLAVES command, which was returning malformed data.
Another fix ensures the ClientSetInfo() method works correctly with Redis 6.2 and above. These are
the kinds of fixes that smooth out rough edges when you're working with complex Redis deployments.
What's being deprecated that I should know about?
A few older methods have been officially marked for deprecation. This is a heads-up to start migrating your code away from them if you're still using them.
The main deprecations are for the setDataSource() method and the BinaryShardedJedis
class. You should plan on updating your code to use their modern replacements to avoid breakage in a future
major release.
FAQ
Does Jedis 4.3 require a specific version of Redis?
No, it maintains backward compatibility.
However, to use the new ACL and JSON commands, you need to be running Redis 6.0+ or 7.0+, respectively.
I use connection pooling. Should I expect any changes?
Your existing code should work fine.
The improvements are internal and aimed at fixing leaks, not changing the public API for pools.
How do I use the new JSON commands?
You use them just like any other command. First, ensure
your Redis server has the RedisJSON module loaded. Then, you can call methods like
jedis.jsonSet("myDoc", "{\"name\":\"John\"}").
What should I use instead of the deprecated BinaryShardedJedis?
The standard
ShardedJedis class is the intended replacement. The binary-specific version is no longer necessary.
Is there a performance boost in this release?
Not directly. The focus was on feature parity,
stability, and bug fixes rather than targeted performance optimizations.