Skip to content

[CALCITE-4803] AggregateProjectMergeRule lost alias after remove the …#2546

Open
xy2953396112 wants to merge 1 commit intoapache:mainfrom
xy2953396112:CALCITE_4803
Open

[CALCITE-4803] AggregateProjectMergeRule lost alias after remove the …#2546
xy2953396112 wants to merge 1 commit intoapache:mainfrom
xy2953396112:CALCITE_4803

Conversation

@xy2953396112
Copy link
Contributor

@xy2953396112 xy2953396112 force-pushed the CALCITE_4803 branch 3 times, most recently from 40ff354 to 9bcb045 Compare September 27, 2021 05:43
() -> "no value found for key " + key + " in " + map));
if (!newKeys.equals(newGroupSet.asList())) {
final List<String> newaggFieldNames = newAggregate.getRowType().getFieldNames();
final List<String> aggFieldNames = aggregate.getRowType().getFieldNames();
Copy link
Contributor

Choose a reason for hiding this comment

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

newaggFieldNames -> newAggFieldNames?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

newaggFieldNames -> newAggFieldNames?

ok, thanks.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

newaggFieldNames -> newAggFieldNames?

I updated the code. Please help review again.Thanks.

@chunweilei chunweilei added the LGTM-will-merge-soon Overall PR looks OK. Only minor things left. label Oct 26, 2021
@NobiGo
Copy link
Contributor

NobiGo commented Nov 1, 2021

Before merge this PR. I think maybe we should reach an agreement in Jira. Because this will be exists confuse in the future.(The code implement is different about the design)

@chunweilei chunweilei added discussion-in-jira There's open discussion in JIRA to be resolved before proceeding with the PR and removed LGTM-will-merge-soon Overall PR looks OK. Only minor things left. labels Nov 2, 2021
@chunweilei
Copy link
Contributor

Before merge this PR. I think maybe we should reach an agreement in Jira. Because this will be exists confuse in the future.(The code implement is different about the design)

Thank you for your kindly reminder. Let us discuss in jira.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

discussion-in-jira There's open discussion in JIRA to be resolved before proceeding with the PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants