[CALCITE-7479] Remove redundant aggregate group keys with FD#4892
[CALCITE-7479] Remove redundant aggregate group keys with FD#4892xiedeyantu wants to merge 2 commits intoapache:mainfrom
Conversation
|
Just draft. |
e303afb to
137af74
Compare
|
mihaibudiu
left a comment
There was a problem hiding this comment.
This looks fine.
How come it is never applicable?
Are all our tests using optimal group by keys?
Or we just don't have many tables with keys?
"How come it is never applicable?" I didn't quite understand the meaning of this sentence. Because the functional dependencies we currently support are limited, I used the primary key as an example. |
|
No other tests were modified |
|
I'm concerned about whether this rewrite is meaningful, as it requires the introduction of |
|
I think there are other uses of |
Because this new rule is not set as a "default" rule, it doesn't have any other impact. |
|
Can you make it default and see what happens? |
Are you suggesting that I don't need to worry too much about "single_value"? Can the compiler do more? |
Of course, I can create a new branch to add it as a default rule and observe the outcome later. |
|
Doesn't even have to be a branch, you can run the experiment and report the results. |
|
There are lots of uses of SINGLE_VALUE, I think that one is fine. |



Jira Link
CALCITE-7479
Changes Proposed