flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <j...@apache.org>
Subject [jira] [Updated] (FLINK-18858) Kinesis Flink SQL Connector
Date Fri, 23 Oct 2020 12:13:00 GMT

     [ https://issues.apache.org/jira/browse/FLINK-18858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

ASF GitHub Bot updated FLINK-18858:
-----------------------------------
    Labels: pull-request-available  (was: )

> Kinesis Flink SQL Connector
> ---------------------------
>
>                 Key: FLINK-18858
>                 URL: https://issues.apache.org/jira/browse/FLINK-18858
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / Kinesis, Table SQL / Ecosystem
>            Reporter: Waldemar Hummer
>            Assignee: Alexander Alexandrov
>            Priority: Major
>              Labels: pull-request-available
>
> Hi all,
> as far as I can see in the [list of connectors|https://github.com/apache/flink/tree/master/flink-connectors],
we have a {{[flink-connector-kinesis|https://github.com/apache/flink/tree/master/flink-connectors/flink-connector-kinesis]}}
for *programmatic access* to Kinesis streams, but there does not yet seem to exist a *Kinesis
SQL connector* (something like {{flink-sql-connector-kinesis}}, analogous to {{flink-sql-connector-kafka}}).
> Our use case would be to enable SQL queries with direct access to Kinesis sources (and
potentially sinks), to enable something like the following Flink SQL queries:
> {code:java}
>  $ bin/sql-client.sh embedded
> ...
> Flink SQL> CREATE TABLE Orders(`user` string, amount int, rowtime TIME) WITH ('connector'
= 'kinesis', ...);
> ...
> Flink SQL> SELECT * FROM Orders ...;
> ...{code}
>  
> I was wondering if this is something that has been considered, or is already actively
being worked on? If one of you can provide some guidance, we may be able to work on a PoC
implementation to add this functionality.
>  
> (Wasn't able to find an existing issue in the backlog - if this is a duplicate, then
please let me know as well.)
> Thanks!



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

Mime
View raw message