[ 
https://issues.apache.org/jira/browse/FLINK-15571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17014238#comment-17014238
 ] 

Yun Tang edited comment on FLINK-15571 at 1/13/20 11:39 AM:
------------------------------------------------------------

[~tgrall] , Flink once had a Redis sink connector and moved to [Apache 
Bahir|https://bahir.apache.org/] three years ago, you can refer to the 
discussion mail 
[here|http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Move-Redis-and-Flume-connectors-to-Apache-Bahir-and-redirect-contributions-there-td13102.html]
 .

Since Redis stream is introduced since Redis-5.0 and different from previous 
Redis sink. I think you could start a discussion in dev mail list to talk about 
whether to introduce a new Redis connector.


was (Author: yunta):
Flink once had a Redis sink connector and moved to [Apache 
Bahir|https://bahir.apache.org/] three years ago, you can refer to the 
discussion mail 
[here|http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Move-Redis-and-Flume-connectors-to-Apache-Bahir-and-redirect-contributions-there-td13102.html]
 .

Since Redis stream is introduced since Redis-5.0 and different from previous 
Redis sink. I think you could start a discussion in dev mail list to talk about 
whether to introduce a new Redis connector.

> Create a Redis Streams Connector for Flink
> ------------------------------------------
>
>                 Key: FLINK-15571
>                 URL: https://issues.apache.org/jira/browse/FLINK-15571
>             Project: Flink
>          Issue Type: New Feature
>          Components: Connectors / Common
>            Reporter: Tugdual Grall
>            Priority: Minor
>
> Redis has a "log data structure" called Redis Streams, it would be nice to 
> integrate Redis Streams and Apache Flink as:
>  * Source
>  * Sink
> See Redis Streams introduction: [https://redis.io/topics/streams-intro]
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to