Hi Maciej,
This is great! I would love to test this out myself and review your Async Sink
implementation.
The best way to get this sink merged in would be to reopen the FLIP, add in
your modifications / implementation details, and drive the FLIP process
forward.
Let's work together to make it official.
- Jeremy
On 6/1/22, 1:40 AM, "Maciej Bryński" <maciej.bryn...@getindata.com> wrote:
CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you can confirm the sender and know the
content is safe.
Hi Jeremy,
We as GetinData already started some work related with HTTP connector.
As a first step we created HTTP Source [1] described in blog post here [2].
During next 3 months we are planning to create HTTP Sink based on Flink
1.15 new Async Sink API.
How can we help with making this sink “official” ?
Regards,
Maciek
[1]:
https://github.com/getindata/flink-http-connector
[2]:
https://getindata.com/blog/data-enrichment-flink-sql-http-connector-flink-sql-part-one/
On 2022/05/17 14:21:31 "Ber, Jeremy" wrote:
> Hi there, We would like to start a discussion thread on FLIP-233:
Introduce HTTP
Connector<https://cwiki.apache.org/confluence/display/FLINK/FLIP-233%3A+Introduce+HTTP+Connector>
where we propose to create a connector for delivering arbitrary data packets
from Apache Flink to an HTTP Endpoint. This connector will give users
flexibility to deliver data to any destination which supports REST endpoints.
This includes REST APIs, Amazon Lambda, users internal or external consumers,
among other options.
>
> Looking forward to your feedback.
>
> Thank you,
> Jeremy Ber
>
>
