[FLINK-13118][jdbc] Introduce JDBC table factory and bridge JDBC table source with streaming table source

[tsreaper]

What is the purpose of the change

Currently JDBCTableSource only implements the LookupableTableSource interface and can only be used as a look-up table source. This PR bridges the table source with the StreamTableSource and ProjectableTableSource interfaces so that JDBCTableSource can also be used as a scan table source.

To create a proper jdbc table source and sink, this PR also introduces a JDBCTableSourceSinkFactory to create the sources and sinks according to the properties specified by users.

Brief change log

• Implement StreamTableSource and ProjectableTableSource interfaces on JDBCTableSource.
• Introduce JDBCTableSourceSinkFactory.

Verifying this change

This change is covered by new IT cases (JDBCTableSourceSinkFactoryITCase).

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

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

Documentation

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

[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 1fee3fb (Tue Aug 06 15:40:27 UTC 2019)

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 for commit fd92602: SUCCESS Build

[JingsongLi]

Thanks @tsreaper for your nice code~ Left some comments.

[flinkbot]

CI report for commit d6fc337: FAILURE Build

[tsreaper]

@wuchong do you need to take a look at the property api?

[flinkbot]

CI report for commit c1af055: FAILURE Build

[flinkbot]

CI report for commit 8d53e27: FAILURE Build

[wuchong]

Thanks @tsreaper , I left some comments.

[flinkbot]

CI report:

• 93aef59 : FAILURE Build

[wuchong]

LGTM. Thanks for the effort @tsreaper .

+1

[wuchong]

Travis passed. https://travis-ci.org/wuchong/flink/builds/557371490