[FLINK-21005][table-api] Introduce new provider for unified Sink API and implement in planner

[SteNicholas]

What is the purpose of the change

FLIP-143 introduced the unified sink API. SinkRuntimeProvider should be added for it and support it in Blink planner. Introduce a new provider SinkProvider for unified Sink API and implement in planner.

Brief change log

• Introduce SinkProvider as a runtime implementation for DynamicTableSink.
• CommonExecSink adds the SinkProvider implement in the createSinkTransformation.

Verifying this change

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): (yes / no)
• The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
• The serializers: (yes / no / don't know)
• The runtime per-record code paths (performance sensitive): (yes / no / don't know)
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / no / don't know)
• The S3 file system connector: (yes / no / don't know)

Documentation

• Does this pull request introduce a new feature? (yes / no)
• If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

[flinkbot]

Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community
to review your pull request. We will use this comment to track the progress of the review.

Automated Checks

Last check on commit 4b0b591 (Fri Feb 19 07:34:06 UTC 2021)

Warnings:

• No documentation files were touched! Remember to keep the Flink docs up to date!

_{Mention the bot in a comment to re-run the automated checks.}

Review Progress

• ❓ 1. The [description] looks good.
• ❓ 2. There is [consensus] that the contribution should go into to Flink.
• ❓ 3. Needs [attention] from.
• ❓ 4. The change fits into the overall [architecture].
• ❓ 5. Overall code [quality] is good.

Please see the Pull Request Review Guide for a full explanation of the review process.

The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot approve description to approve one or more aspects (aspects: description, consensus, architecture and quality)
• @flinkbot approve all to approve all aspects
• @flinkbot approve-until architecture to approve everything until architecture
• @flinkbot attention @username1 [@username2 ..] to require somebody's attention
• @flinkbot disapprove architecture to remove an approval you gave earlier

[flinkbot]

CI report:

• f555e1a Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run travis re-run the last Travis build
• @flinkbot run azure re-run the last Azure build

[wuchong]

Thanks for the contribution.

Could you also add a test for this? You can add the sink provider implementation in org.apache.flink.table.planner.factories.TestFileSourceFactory. It wraps the FileSource as a SourceProvider. I think you can also wrap the FileSink as a SinkProvider. And then you can add IT case in org.apache.flink.table.planner.runtime.stream.table.TableSinkITCase.

[wuchong]

Thanks for the updating @SteNicholas . It looks in a good shape now. I think we can further refactor the implementaion of createSinkTransformation, it is quite long and messed. I refactored it to extract the logic of applying not-null-enforcer and keyBy partition. You can see the changes in my commit: wuchong@0894736

[wuchong]

LGTM.