[
https://issues.apache.org/jira/browse/BAHIR-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
João Boto updated BAHIR-160:
----------------------------
Fix Version/s: Flink-1.2.0
(was: Flink-1.1.0)
> Allow 'low level' Redis commands for the Redis Flink Connector
> --------------------------------------------------------------
>
> Key: BAHIR-160
> URL: https://issues.apache.org/jira/browse/BAHIR-160
> Project: Bahir
> Issue Type: Improvement
> Components: Flink Streaming Connectors
> Affects Versions: Flink-1.0
> Reporter: David Maier
> Priority: Major
> Fix For: Flink-1.2.0
>
>
> Hello,
> would it be possible to allow the usage of more than the currently wrapped
> commands in the flink connector?
> Background is that Redis is now supporting modules. Each module can have a
> specific set of own commands.
> The connector seems to rely on Jedis. Jedis is allowing to execute any kind
> of command by providing the 'sendCommand(...)' method as part of the
> BinaryClient class. Here an example:
>
> {code:java}
> jedis.getClient().sendCommand(...){code}
>
> Further details can be found here:
> [https://github.com/xetorthio/jedis/blob/master/src/main/java/redis/clients/jedis/BinaryClient.java]
> .
>
> It seems that the class RedisContainer
> ([https://github.com/apache/bahir-flink/blob/master/flink-connector-redis/src/main/java/org/apache/flink/streaming/connectors/redis/common/container/RedisContainer.java])
> implements only a portion of the possible Redis commands. So it would be
> actually great to have 'sendCommand' as one of the wrapped methods in order
> to leverage specific Module functionality on the server side.
> I didn't dig too deep into the command mapping part yet, but do you think
> this is a feasible?
> Regards,
> David Maier
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
