5.0.0

[sazzad16]

What's New?

Automatic Cross-Cluster Failover

We're happy to introduce the Cross-Cluster Failover feature in Jedis. This feature provides high availability and resilience by allowing seamless transitions between Redis clusters during unforeseen failures or downtimes. It's a built-in tool to minimize manual intervention and downtime and ensure a more resilient application infrastructure.
Learn more about how you can automate the failover process in our documentation.

Full Redis 7.2 and RESP3 Support

Examples to enable RESP3 are included later in this release note.

---

Changes

🔥 Breaking Changes (Listed here)

🚀 New Features

• Support RESP3 ([WIP] RESP3 Support #3293, More RESP3 coverage #3387, Pub/Sub on RESP3 #3388, Re-use Pub/Sub codes #3389, Support RESP3 protocol through URI/URL #3403, Use RedisCredentials with HELLO command #3507)
• Support Sharded PubSub (Support Sharded PubSub #3396)
• Introduce PipelineBase for Pipeline and multi node pipeline classes (Introduce PipelineBase for Pipeline and multi node pipeline classes #3437, Polish 'pipelined()' in UnifiedJedis #3442)
• 'double' timeout parameter for BLMPOP and BZMPOP commands ('double' timeout parameter for BLMPOP and BZMPOP #3444)

🧪 Experimental Features

• Cross cluster failover (Cross cluster failover #3310)
• Allow setting default dialect for RediSearch module (Allow setting default dialect for search module #3452)
• Support JSON.MERGE command (Support JSON.MERGE Command #3429)
• Support TOPK.LIST with WITHCOUNT option (Support TOPK.LIST with WITHCOUNT option #3495)

🐛 Bug Fixes

• Fix return value of HRANDFIELD with values when count is negative ( Fix return value of HRANDFIELD With Values when count is negative #3425, Polishing #3425 and some tests #3430)
• Return List instead of Set in ZDIFF, ZINTER, ZUNION commands (Return List instead of Set in ZDIFF, ZINTER, ZUNION #3431)

🧰 Maintenance

• Deprecate RedisJSON v1 support (Deprecate RedisJSON v1 support #3503)
• Deprecate RedisGraph support (Deprecate RedisGraph support #3504)
• Deprecate Sharding/Sharded feature (Deprecate Sharding/Sharded feature #3386)
• Bump org-json:json from 20230227 to 20230618 (Bump json from 20230227 to 20230618 #3472)

---

RESP3 Examples

This release introduces enabling RESP3 Redis connection, when the Redis server supports it.

1. Enable RESP3 to a UnifiedJedis object:

import redis.clients.jedis.DefaultJedisClientConfig;
import redis.clients.jedis.HostAndPort;
import redis.clients.jedis.UnifiedJedis;

class DoResp3 {
    public static void main() {
        HostAndPort hnp = HostAndPort.from("localhost:6379");
        UnifiedJedis c =  UnifiedJedis(hnp, DefaultJedisClientConfig.builder().resp3().build());
        c.set("foo", "value!");
        c.get("foo");
    }
}

2. Enable RESP3 to a Jedis object:

import redis.clients.jedis.DefaultJedisClientConfig;
import redis.clients.jedis.HostAndPort;
import redis.clients.jedis.Jedis;

class DoResp3 {
    public static void main() {
        HostAndPort hnp = HostAndPort.from("localhost:6379");
        Jedis c =  Jedis(hnp, DefaultJedisClientConfig.builder().resp3().build());
        c.set("foo", "value!");
        c.get("foo");
    }
}

---

This discussion was created from the release 5.0.0.

[wp973]

Does jedis(5.0.0) support tracking?

How can jedis client listen the "push" messages? 🧐 @sazzad16

[wp973]

I'm going to do a POC about tracking by "push" message, is this possible?

[wp973]

Thank you for your reply!

[sazzad16]

Possible? Yes.

[wp973]

Do you have any plans to support "tracking"?

[wp973]

I'm thinking of using the approach of two connections mode: https://redis.io/docs/manual/client-side-caching/#two-connections-mode.

Because implementing push messages may break requests/response model ingrained in the source code of the library.

@sazzad16

[wp973]

About "push" messgae

Redis conf: https://redis.io/docs/reference/protocol-spec/#pushes

RESP3: https://github.com/redis/redis-specifications/blob/master/protocol/RESP3.md

[chenshi5012]

like to see aggregation search features in 5.x !!

[sazzad16]

@chenshi5012 Please explain. Jedis already has FT.AGGREGATE command support.
It also has ...Iteration group of methods allowing to aggregate results from all nodes.