This page is meant as a template for writing a FLIP related to a new Flink connector. To create a FLIP choose Tools->Copy on this page and modify with your content and replace the heading with the next FLIP number and a description of your issue. Replace anything in italics with your own description.
...
| Page properties |
|---|
...
Document the state by adding a label to the FLIP page with one of "discussion", "accepted", " |
...
released", " |
...
rejected" |
...
.
|
...
|
...
...
|
|
...
|
Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).
Motivation
Describe Shortly describe the problems system that your connector is trying to solve.
Public Interfaces
will connect to. In case there is already a connector available, please explain why you're introducing either a new one or an improvement via this FLIP.
Public Interfaces
Please include the Flink interfaces that you will use when implementing your connector. You most likely will use one or more of these:
- Source:
- Sink:
Briefly list any new interfaces that will be introduced as part of this proposal or any existing interfaces that will be removed or changed. The purpose of this section is to concisely call out the public contract that will come along with this connector.
...
Describe the new connector you are proposing in appropriate detail. This may be fairly extensive and have large subsections of its own. Or it may be a few sentences. Use judgement based on the scope of the change. Please include details on implementation including what destinations your connector will support, batch and stream support, async or synchronous connector implementation, etc.
We aim to have connectors that meet the following criteria (where applicable):
- Source and Sink
- Supports both Bounded (Batch) and Unbounded (Streaming)
- Usable in both DataStream and Table API/SQL
Compatibility, Deprecation, and Migration Plan
...