Support issuing Latency commands

[CodingFabian]

Currently it is not possible to issue latency commands using jedis. You need to write your own client to issue custom commands.
There are a couple of latency commands (latency history, latency latest) that could be executed. ideally automatically guarded against the redis version (2.8.13 +)

[marcosnils]

@CodingFabian good catch. As you seem to need these commands, what do you think about crafting a PR so Jedis can include this functionality?

[CodingFabian]

Sure, I am just a bit lost where this should go:
JedisCommands, MultiKeyCommands, AdvancedJedisCommands, ScriptingCommands, BasicCommands, ClusterCommands, SentinelCommands ?

[marcosnils]

@CodingFabian I'd start adding it in the BasicCommands interface and move from there.

[sheinbergon]

@marcosnils what's the status of this feature request ? Has this been implemented yet ?

[marcosnils]

@sheinbergon there's no open PR, so no. @CodingFabian ping?

[CodingFabian]

Nope, havent done anything so far.

[sheinbergon]

@marcosnils feel free to assign this to me . I will work on it in the upcoming weeks 👍

[CodingFabian]

cool thanks!

[marcosnils]

@sheinbergon no need to assign, maybe @CodingFabian wanted/needed to implement it?. @CodingFabian ?

[sheinbergon]

@CodingFabian I'm guessing you'd like to support LATENCY LATEST , LATENCY HISTORY and LATENCY RESET , right ? Is there anything I missed ?

@marcosnils would you like to add anything else ?

[sheinbergon]

@CodingFabian @marcosnils ?

[marcosnils]

@sheinbergon go ahead and implement it @CodingFabian timed out.

[CodingFabian]

I actually had a weekend.
yes. LATENCY LATEST and LATENCY HISTORY is what we wanted.

[github-actions]

This issue is marked stale. It will be closed in 30 days if it is not updated.

[Lcarrot]

Hello, can i try to solve this issue?