-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-6397][SQL] Check the missingInput simply #5082
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
Conversation
|
Can one of the admins verify this patch? |
a58eda9 to
25766b9
Compare
|
greate improvement! |
|
test this please |
|
Test build #28947 has started for PR 5082 at commit
|
|
Test build #28947 has finished for PR 5082 at commit
|
|
Test PASSed. |
|
@liancheng @marmbrus Any more comment on this? |
|
LGTM, #5129 also needs this one. I'm merging this to master and branch-1.3. Thanks for working on this! |
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.
Why do we prefer adding missingInput in Expand? At first I thought we should just update QueryPlan.missingInput to take the grouping ID virtual column into account.
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.
@liancheng The grouping ID virtual column only used in Expand(LogicalPlan), so I think it's better to add the grouping ID virtual column in subclass(Expand) of QueryPlan. If add missingInput in QueryPlan, it will be more and more when other case like the grouping ID virtual column.
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.
My point is we may also support other virtual columns like INPUT__FILE__NAME and BLOCK__OFFSET__INSIDE__FILE in the future. These virtual columns can be used in more general places like Project and Filter. That's why I think moving this to QueryPlan may make more sense.
|
Sorry, just reverted my last merge, please see my comment above. |
|
@watermen A little off topic, would you mind to set your name properly by executing this: Currently your name shows as |
|
@liancheng Thanks, I'll do it. |
#5082 /cc liancheng Author: Yadong Qi <[email protected]> Closes #5132 from watermen/sql-missingInput-new and squashes the following commits: 1e5bdc5 [Yadong Qi] Check the missingInput simply (cherry picked from commit 9f3273b) Signed-off-by: Cheng Lian <[email protected]>
#5082 /cc liancheng Author: Yadong Qi <[email protected]> Closes #5132 from watermen/sql-missingInput-new and squashes the following commits: 1e5bdc5 [Yadong Qi] Check the missingInput simply
No description provided.