-
Notifications
You must be signed in to change notification settings - Fork 28.2k
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
[SPARK-24548][SQL] Fix incorrect schema of Dataset with tuple encoders #21576
Conversation
Test build #91903 has finished for PR 21576 at commit
|
retest this please. |
Test build #91919 has finished for PR 21576 at commit
|
retest this please. |
Test build #91921 has finished for PR 21576 at commit
|
retest this please |
Test build #91932 has finished for PR 21576 at commit
|
retest this please |
Test build #91945 has finished for PR 21576 at commit
|
retest this please. |
Test build #91951 has finished for PR 21576 at commit
|
Is Jenkins unstable? The building error looks weird... |
retest this please. |
Test build #91953 has finished for PR 21576 at commit
|
cc @cloud-fan Do you have idea about the building error message? |
Seems the building for other PRs are also failed. |
One of my PRs has the same problem. When tried to compile more than 20 times, only one try went into the test phase. |
retest this please. |
Test build #91977 has finished for PR 21576 at commit
|
retest this please |
@HyukjinKwon Looks it passes building now. |
Test build #92020 has finished for PR 21576 at commit
|
cc @cloud-fan for review. |
thanks, merging to master! |
What changes were proposed in this pull request?
When creating tuple expression encoders, we should give the serializer expressions of tuple items correct names, so we can have correct output schema when we use such tuple encoders.
How was this patch tested?
Added test.