Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FLINK-12170] [table-planner-blink] Add support for generating optimized logical plan for Over aggregate #8157

Merged
merged 4 commits into from
Apr 17, 2019

Conversation

godfreyhe
Copy link
Contributor

What is the purpose of the change

Add support for generating optimized logical plan for Over aggregate

Brief change log

  • Adds physical rules to convert logical over aggregate to physical over aggregate
  • Adds more aggregate functions, including RANK, DENS_ERANK, ROW_NUMBER

Verifying this change

This change added tests and can be verified as follows:

  • Added test that validates that the over aggregate physical plan

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 documented)

@flinkbot
Copy link
Collaborator

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

Expression[] orderKeyEquals = new Expression[orderKeyTypes.length];
for (int i = 0; i < orderKeyTypes.length; ++i) {
Expression lasValue = lastValues[i];
// if (lastValue is null) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

delete these?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are comments, just look like code. I have deleted them.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, my bad, i think it makes sense to keep this as comment, it can help us understand the logic

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have reverted them


@Override
public int operandCount() {
return 1;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be 0?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

good catch!

Copy link
Contributor

@KurtYoung KurtYoung left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

03:56:40.290 [ERROR] Tests run: 966, Failures: 87, Errors: 0, Skipped: 0

There are a lot of test failures

@godfreyhe
Copy link
Contributor Author

03:56:40.290 [ERROR] Tests run: 966, Failures: 87, Errors: 0, Skipped: 0

There are a lot of test failures

Sorry, I forget to move the test result xml files to table/plan/batch/sql/agg path after I move HashAggregateTest and SortAggregateTest from table.plan.batch.sql package to table.plan.batch.sql.agg package.

@KurtYoung KurtYoung merged commit e42f6b5 into apache:master Apr 17, 2019
tianchen92 pushed a commit to tianchen92/flink that referenced this pull request May 13, 2019
@godfreyhe godfreyhe deleted the FLINK-12170 branch June 1, 2019 09:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants