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

[Bugfix] keep the aggregate expr order when rewrite aggregate operator #7657

Merged

Conversation

stdpain
Copy link
Contributor

@stdpain stdpain commented Jun 22, 2022

What type of PR is this:

  • bug
  • feature
  • enhancement
  • refactor
  • others

Which issues of this PR fixes :

Fixes #7659

Problem Summary(Required) :

we should keep the aggregate expr order when rewrite, because we will use
singleDistinctFunctionPos to decide call update or merge

stdpain added 2 commits June 22, 2022 05:14
we should keep the aggregate expr order when rewrite, because we will use
singleDistinctFunctionPos to decide call update or merge
@wanpengfei-git
Copy link
Collaborator

[FE PR Coverage check]

😍 pass : 8 / 8 (100.00%)

file detail

path covered line new line coverage
🔵 com/starrocks/sql/optimizer/rewrite/AddDecodeNodeForDictStringRule.java 8 8 100.00%

@stdpain stdpain merged commit 3fadd41 into StarRocks:main Jun 23, 2022
@stdpain
Copy link
Contributor Author

stdpain commented Jun 23, 2022

https://github.com/Mergifyio backport branch-2.1

mergify bot pushed a commit that referenced this pull request Jun 23, 2022
#7657)

we should keep the aggregate expr order when rewrite, because we will use
singleDistinctFunctionPos to decide call update or merge

(cherry picked from commit 3fadd41)

# Conflicts:
#	fe/fe-core/src/test/java/com/starrocks/sql/plan/DecodeRewriteTest.java
@mergify
Copy link
Contributor

mergify bot commented Jun 23, 2022

backport branch-2.1

✅ Backports have been created

stdpain added a commit to stdpain/starrocks-2 that referenced this pull request Jun 23, 2022
…rewrite aggregate operator (StarRocks#7657)

we should keep the aggregate expr order when rewrite, because we will use
singleDistinctFunctionPos to decide call update or merge
@stdpain
Copy link
Contributor Author

stdpain commented Jun 23, 2022

https://github.com/Mergifyio backport branch-2.2

mergify bot pushed a commit that referenced this pull request Jun 23, 2022
#7657)

we should keep the aggregate expr order when rewrite, because we will use
singleDistinctFunctionPos to decide call update or merge

(cherry picked from commit 3fadd41)

# Conflicts:
#	fe/fe-core/src/test/java/com/starrocks/sql/plan/DecodeRewriteTest.java
@mergify
Copy link
Contributor

mergify bot commented Jun 23, 2022

backport branch-2.2

✅ Backports have been created

stdpain added a commit to stdpain/starrocks-2 that referenced this pull request Jun 23, 2022
…rewrite aggregate operator (StarRocks#7657)

we should keep the aggregate expr order when rewrite, because we will use
singleDistinctFunctionPos to decide call update or merge
@stdpain
Copy link
Contributor Author

stdpain commented Jun 23, 2022

https://github.com/Mergifyio backport branch-2.3

@mergify
Copy link
Contributor

mergify bot commented Jun 23, 2022

backport branch-2.3

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Jun 23, 2022
#7657)

we should keep the aggregate expr order when rewrite, because we will use
singleDistinctFunctionPos to decide call update or merge

(cherry picked from commit 3fadd41)
stdpain added a commit that referenced this pull request Jun 23, 2022
#7657)

we should keep the aggregate expr order when rewrite, because we will use
singleDistinctFunctionPos to decide call update or merge

(cherry picked from commit 3fadd41)
kangkaisen pushed a commit that referenced this pull request Jun 23, 2022
…rewrite aggregate operator (#7657) (#7690)

we should keep the aggregate expr order when rewrite, because we will use
singleDistinctFunctionPos to decide call update or merge
kangkaisen pushed a commit that referenced this pull request Jun 23, 2022
…rewrite aggregate operator (#7657) (#7688)

we should keep the aggregate expr order when rewrite, because we will use
singleDistinctFunctionPos to decide call update or merge
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

wrong plan in 3 stage aggregate with lowcardinality optimazation
4 participants