-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-19005][SQL] Keep column ordering when a schema is explicitly specified #16410
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
|
Test build #70613 has finished for PR 16410 at commit
|
|
I'm looking into the failure... |
|
Test build #70630 has finished for PR 16410 at commit
|
|
This fix change some existing behaviour in datasource. I'm not sure this is acceptable, so welcome any advices. |
|
This behavior is intentional and already published, we can not change it. What we should do is to find out other places that don't follow this rule and respect the given schema, i.e. you are doing the opposite thing. |
|
Aha, okay and I'll fix that way. Thanks! |
|
Test build #71269 has finished for PR 16410 at commit
|
This reverts commit 466c59067042538619a0ddc9e89014d9f97482ea.
This reverts commit 9174e7c0686ddcd963a0232250dbcc50062d750b.
|
Test build #71308 has finished for PR 16410 at commit
|
|
Test build #71309 has finished for PR 16410 at commit
|
|
Test build #71311 has finished for PR 16410 at commit
|
|
Test build #71312 has finished for PR 16410 at commit
|
|
Test build #71326 has finished for PR 16410 at commit
|
|
Jenkins, retest this please. |
1 similar comment
|
Jenkins, retest this please. |
|
Test build #71336 has finished for PR 16410 at commit
|
|
Test build #71367 has started for PR 16410 at commit |
|
Jenkins, retest this please. |
|
Test build #71369 has finished for PR 16410 at commit
|
|
I looked around the code and then I though this is an expected behaviour, so I'll close this. Thanks! |
|
Test build #71385 has finished for PR 16410 at commit
|
What changes were proposed in this pull request?
This pr is to keep column ordering when a schema is explicitly specified.
A concrete example is as follows;
This fix removes the code to filter out the overlapped fields of a data schema in
getOrInferFileFormatSchema. Then, it respects column ordering inHadoopFsRelation#schema.How was this patch tested?
Added tests in
ParquetPartitionDiscoverySuite.This pr comes from SPARK-18108(#16030).