[FLINK-15089][connectors] Puslar catalog

[yjshen]

What is the purpose of the change

This PR implements Pulsar catalog which is part of FLIP-72.

The Pulsar catalog supports the following features by extending AbstractCatalog API:

• Open and close the catalog
• Database operations: list, get, exists, create, drop (create and drop should first check if the user has sufficient permissions)
• Table operations: list, get, exist, create, drop (create and drop should first check if the user has sufficient permissions)

Brief change log

• The main functionality of Catalog exists in PulsarCatalog and PulsarMetadataReader.
• Pulsar Schema <-> Flink type conversion exists in SchemaUtils.

Verifying this change

This PR will be tested by unit tests and integration tests.

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

• Dependencies (does it add or upgrade a dependency): (yes) . Add Pulsar dependencies.
• 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? (yes)
• If yes, how is the feature documented? (https://docs.google.com/document/d/1LMnABtXn-wQedsmWv8hopvx-B-jbdr8-jHbIiDhdsoE/edit?usp=sharing)

[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 206bb09 (Fri Dec 06 06:58:15 UTC 2019)

Warnings:

• 2 pom.xml files were touched: Check for build and licensing issues.
• No documentation files were touched! Remember to keep the Flink docs up to date!
• This pull request references an unassigned Jira ticket. According to the code contribution guide, tickets need to be assigned before starting with the implementation work.

_{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:

• 72bbd5f Travis: FAILURE Azure: FAILURE

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

[yjshen]

@bowenli86 Hi Bowen, I've updated the PR with tests. Could you please help review it? Thanks!

[yjshen]

@bowenli86 Hi Bowen, I've updated the PR with tests. Could you please help review it? Thanks!

[bowenli86]

hi @yjshen sorry for the late response, I'm really busy right now and may have some time later April to take a detailed look. Can you try to find some other committers to help review?

[KurtYoung]

Hi @yjshen , sorry for the late response on this. I think right now the community is busy with finishing 1.11 planned features thus don't have much capacity for reviewing this. I would raise this during 1.12 feature planning and hopefully we can get this and pulsar connectors in Flink 1.12.

[yjshen]

Hi @bowenli86 @KurtYoung, thanks for the update. Looking forward to further discussions on this PR.