-
Notifications
You must be signed in to change notification settings - Fork 606
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
Implement excess key columns drop for BlockMapJoinCore computation node #9036
Implement excess key columns drop for BlockMapJoinCore computation node #9036
Conversation
⚪
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
⚪ ⚪
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
ecdd0f2
to
8970a44
Compare
⚪
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
⚪ ⚪
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
8970a44
to
102ed94
Compare
⚪ ⚪
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
⚪
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
!
102ed94
to
0cb5832
Compare
⚪
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
⚪ ⚪
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
This patchset implements drop of the specified key columns, to reduce excess data in the result, produced by the
BlockMapJoinCore
computation node. As a result of the patch, program builder handler forBlockMapJoinCore
accepts the vector with the specified key columns, that match indices of the corresponding "left" wide flow fields.It's worth mentioning why only left key columns are processed:
All in all, only the key columns used to process the join, but not required in the output type, should be processed by this computation node.
NB: MKQL version is not bumped, since there is no way to emit
BlockMapJoinCore
at the moment.Changelog category