Last checked and updated on 10 Jun 2026
What Is New in Jedis 5.0
Jedis 5.0 is a major release that introduces new Redis command APIs, drops support for older Java versions, and streamlines the client's architecture. This version focuses on modernizing the library to align with current Redis server capabilities and Java development practices.
| Category | Key Changes |
|---|---|
| New Features | New unified command API, Support for Redis 7.x commands |
| Improvements | Java 8 baseline, Simplified connection handling, Deprecated method removal |
| Breaking Changes | Dropped Java 7 support, Removed deprecated classes and methods |
What's the new command API structure?
Jedis 5.0 introduces a new, more intuitive command API that groups related Redis operations. This replaces the older, more fragmented method organization and provides a cleaner interface for developers.
The new structure separates commands into logical groups like JedisCommands, ListCommands, and SetCommands. This makes it easier to discover and use related functionality without digging through a massive single interface.
In practice, you'll now access commands through dedicated interfaces rather than the monolithic Jedis class. This matters because it creates a more maintainable codebase and better aligns with how developers think about Redis operations.
Why did Java version requirements change?
Jedis 5.0 now requires Java 8 as the minimum version, dropping support for Java 7. This change allows the library to leverage modern Java features and language improvements that weren't available in older versions.
The upgrade to Java 8 enables better performance, cleaner code through lambdas and streams, and access to improved APIs. For teams still on Java 7, this means you'll need to either upgrade your Java version or remain on Jedis 4.x.
This shift reflects the broader Java ecosystem's move toward modern runtime environments. Most production systems have been on Java 8+ for years, so this change affects very few active deployments.
How were deprecated elements handled?
The release removes all previously deprecated classes, methods, and configuration options that were marked for deletion. This cleanup reduces technical debt and makes the library more maintainable going forward.
Removed elements include the old ShardedJedis implementation, various deprecated methods across different classes, and outdated configuration parameters. The team provided migration paths in earlier releases, giving developers ample time to adapt.
If you're upgrading from Jedis 4.x, you'll need to check your code for any usage of deprecated features. The compiler will help identify these breaking changes during compilation.
What Redis 7 features are supported?
Jedis 5.0 adds support for several Redis 7.x commands and features that weren't available in previous versions. This includes functionality around JSON manipulation, time series data, and enhanced search capabilities.
New command support includes operations for Redis JSON, Redis Search, and other modules that have become standard in recent Redis deployments. The implementation follows the same pattern as the new command API structure.
This update matters because it ensures Jedis keeps pace with Redis server developments. You can now use the latest Redis features without waiting for client library updates.
FAQ
Is Jedis 5.0 compatible with Redis 6.x servers?
Yes, Jedis 5.0 maintains full backward compatibility with Redis 6.x servers. The new features specifically designed for Redis 7.x will simply not be available when connected to older server versions.
What's the migration path from ShardedJedis?
If you were using ShardedJedis, you should migrate to the newer cluster API or consider using Redis Cluster directly. The removal forces adoption of more modern and supported approaches to distributed Redis.
Does the new API affect connection pooling?
The connection pooling mechanism remains largely unchanged. The improvements focus on the command interface rather than the underlying connection management, so existing pooling configurations should continue to work.
Are there any performance improvements in this release?
While not specifically highlighted as a performance release, the cleanup of deprecated code and modernized internals may provide minor performance benefits. The main improvements are in API design and maintainability.
Can I use both old and new API styles during migration?
No, the old API methods have been completely removed in Jedis 5.0. You'll need to complete your migration to the new API style before upgrading, or do the refactoring after upgrading to version 5.0.