Skip to content

Keep QP info for various cases in ProjectPushDown#603

Open
kentthang010 wants to merge 2 commits intomainfrom
594-projectpushdown-keep-query-planning-info-if-possible
Open

Keep QP info for various cases in ProjectPushDown#603
kentthang010 wants to merge 2 commits intomainfrom
594-projectpushdown-keep-query-planning-info-if-possible

Conversation

@kentthang010
Copy link
Copy Markdown
Collaborator

Addresses the ProjectPushDown part of #594.

@kentthang010 kentthang010 linked an issue May 4, 2026 that may be closed by this pull request
11 tasks
@kentthang010 kentthang010 requested a review from hartig May 4, 2026 09:01
Copy link
Copy Markdown
Member

@hartig hartig left a comment

Choose a reason for hiding this comment

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

I didn't manage to go through everything, but I added some comments. After addressing them, please revisit the other cases (for which I don't have comments because I didn't manage to look at them) and think about them once more in the light of my comments about the mayReduce flag. Some of them might also be affected by the mayReduce flag (or may be not--just double check).

@kentthang010
Copy link
Copy Markdown
Collaborator Author

kentthang010 commented May 6, 2026

Latest commit resolves the comments above.

I also went over the other cases and considered the mayReduce flag.

In summary, the pushdowns that now consider mayReduce are:

  • createPlanForUnaryOpUnderProjectPreserveQP
  • Case 1 (full pushdown) for createPlanForAddOpUnderProject
  • createPlanForProjectUnderProject
  • createPlanForUnfoldUnderProject

I don't think I have to check mayReduce for createPlanForBindUnderProject.

@kentthang010 kentthang010 requested a review from hartig May 6, 2026 13:55
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.

2 participants