[FLINK-11834] [table-planner-blink] Introduce flink logical relational nodes

[godfreyhe]

What is the purpose of the change

Introduce flink logical relational nodes.
This commit includes most flink logical relational nodes, the rest will be introduced by other commit.

Brief change log

• Adds nodes extended from Calcite, including FlinkLogicalAggregate, FlinkLogicalCalc, FlinkLogicalCorrelate, FlinkLogicalIntersect, FlinkLogicalJoin, FlinkLogicalMinus, FlinkLogicalOverWindow, FlinkLogicalSort, FlinkLogicalUnion, FlinkLogicalValues, FlinkLogicalTableSourceScan, FlinkLogicalTableFunctionScan
• Adds new RelNode for Flink, including Expand, Rank, Sink, WatermarkAssigner

Verifying this change

This change is an initialization work without any test coverage.

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? (yes)
• If yes, how is the feature documented? (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.

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

[KurtYoung]

LGTM, i only have one minor comment

[KurtYoung]

Looks like this is a part of your Rank rel node, i think should not belong to util

[godfreyhe]

RankRange can be moved into Rank.scala file

[godfreyhe]

FlinkLogicalTableSourceScan is also added into this commit. The rest flink logical nodes(contains: FlinkLogicalWindowAggregate, FlinkLogicalSnapshot, FlinkLogicalSemiJoin, FlinkLogicalMatch ) will be introduced later because they depend on Expression or Calcite change.

[KurtYoung]

I think you can open a jira to track all unmerged logical nodes

[godfreyhe]

related issues:
https://issues.apache.org/jira/browse/FLINK-11839
https://issues.apache.org/jira/browse/FLINK-11840
https://issues.apache.org/jira/browse/FLINK-11841
https://issues.apache.org/jira/browse/FLINK-11842