Support late materialization

[Lloyd-Pottiger]

Signed-off-by: Lloyd-Pottiger [email protected]

What problem does this PR solve?

Issue Number: ref #5829

Problem Summary:

What is changed and how it works?

RFC: pingcap/tidb#39654

1. Support push down filters in storage layer
2. Refine extra cast actions

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)

# tpch-1
> tiup bench tpch prepare
> tiup bench tpch run --check #pass
> tiup bench tpch run --check --conn-params tidb_enable_late_materialization=ON #pass

# clickbench
> AWS_ACCESS_KEY_ID=xxx AWS_SECRET_ACCESS_KEY=xxx tiup br restore table --db hits -s s3://benchmark/clickbench-hits --s3.endpoint http://xxx.xx/ --send-credentials-to-tikv=true --pd ${pd_ip}:${pd_port} --table hits
> mysql --host xxx --port < clickbench.sql > output # master
> mysql --host xxx --port < clickbench.sql > output1 # this pr, set tidb_enable_late_materialization=ON
> git diff --no-index output output1

• No code

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Support late materialization, push down some predicates to storage layer to reduce the amount of data to be read.

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• hongyunyan
• windtalker

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[Lloyd-Pottiger]

/run-all-tests

[Lloyd-Pottiger]

/run-all-tests

[Lloyd-Pottiger]

/run-all-tests

[windtalker]

Should update the pr description.

[windtalker]

Should not change the type of source_columns here

[Lloyd-Pottiger]

should change. a, b, c, cast_c -> a, b, c, here, cast_c is renamed to c, so source_columns[2].type should equal to cast_c's type

[windtalker]

Then it is a little hack compare to the original implementation, how about we still change the name to cast_c, and let the following project to rename cast_c to c?

[Lloyd-Pottiger]

It's ok. But why this is hack? IMHO, It is normal projection, which aims to replace original c with cast_c.

case PROJECT:
{
    Block new_block;

    for (const auto & projection : projections)
    {
        const std::string & name = projection.first;
        const std::string & alias = projection.second;
        ColumnWithTypeAndName column = block.getByName(name);
        if (!alias.empty())
            column.name = alias;
        new_block.insert(std::move(column));
    }

    block.swap(new_block);

    break;
}

[windtalker]

Compute part LGTM

[Lloyd-Pottiger]

/merge

[ti-chi-bot]

@Lloyd-Pottiger: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: a77301a

[ti-chi-bot]

@Lloyd-Pottiger: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

trigger some heavy tests which will not run always when PR updated.

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[Lloyd-Pottiger]

/run-integration-test