[FLINK-21531][table-planner-blink][table-api-java][hive] Introduce pluggable Parser

[lirui-apache]

What is the purpose of the change

Introduce pluggable Parser and add simple implementation for hive.

Brief change log

• Add ParserFactory interface
• Add DefaultParserFactory to create ParserImpl
• Create Parser instance according to dialect in PlannerBase
• Don't hold a constant Parser instance in TableEnvironmentImpl
• Add HiveParserFactory to create HiveParser
• Add test case

Verifying this change

Existing and added test cases

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, Kubernetes/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? NA

[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 e096dad (Mon Mar 01 07:46:58 UTC 2021)

Warnings:

• 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:

• e096dad UNKNOWN
• a34809a 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

[wuchong]

Thanks @lirui-apache . I only left a minor comment. Others looks good to me.

[wuchong]

Could you assert the class name of the new parser? Asserting same object may not safe, because the underlying may return a new HiveParser instance.

[lirui-apache]

Thanks @wuchong for your comment. I have updated the PR accordingly.

[wuchong]

LGTM.

[wuchong]

The failed e2e test is not related to this PR.

Merging...