-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-16044][SQL] Backport input_file_name() for data source based on NewHadoopRDD to branch 1.6 #13806
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 #60926 has finished for PR 13806 at commit
|
|
retest this please |
|
Test build #60927 has finished for PR 13806 at commit
|
|
retest this please |
|
Test build #60935 has finished for PR 13806 at commit
|
|
Test build #3121 has finished for PR 13806 at commit
|
|
Test build #3122 has finished for PR 13806 at commit
|
|
Test build #3123 has finished for PR 13806 at commit
|
|
It seems the error is not related with this change. |
|
I will re-run this test here and meanwhile I will try to build in my local and run the Python tests. |
|
retest this please |
|
Test build #60990 has finished for PR 13806 at commit
|
|
I guess it is about f4af6a8. I will look into this deeper. |
…oot` module ending up failure of Python tests ## What changes were proposed in this pull request? This PR fixes incorrect checking for `root` module (meaning all tests). I realised that #13806 is being failed due to this one. The PR corrects two files in `sql` and `core`. Since it seems fixing `core` module triggers all tests by `root` value from `determine_modules_for_files`. So, `changed_modules` becomes as below: ``` ['root', 'sql'] ``` and `module.dependent_modules` becaomes as below: ``` ['pyspark-mllib', 'pyspark-ml', 'hive-thriftserver', 'sparkr', 'mllib', 'examples', 'pyspark-sql'] ``` Now, `modules_to_test` does not include `root` and this checking is skipped but then both `changed_modules` and `modules_to_test` are being merged after that. So, this includes `root` module to test. This ends up with failing with the message below (e.g. https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60990/consoleFull): ``` Error: unrecognized module 'root'. Supported modules: pyspark-core, pyspark-sql, pyspark-streaming, pyspark-ml, pyspark-mllib ``` ## How was this patch tested? N/A Author: hyukjinkwon <[email protected]> Closes #13845 from HyukjinKwon/fix-build-1.6.
|
Jenkins, retest this please. |
…oot` module ending up failure of Python tests ## What changes were proposed in this pull request? This PR fixes incorrect checking for `root` module (meaning all tests). I realised that apache#13806 is being failed due to this one. The PR corrects two files in `sql` and `core`. Since it seems fixing `core` module triggers all tests by `root` value from `determine_modules_for_files`. So, `changed_modules` becomes as below: ``` ['root', 'sql'] ``` and `module.dependent_modules` becaomes as below: ``` ['pyspark-mllib', 'pyspark-ml', 'hive-thriftserver', 'sparkr', 'mllib', 'examples', 'pyspark-sql'] ``` Now, `modules_to_test` does not include `root` and this checking is skipped but then both `changed_modules` and `modules_to_test` are being merged after that. So, this includes `root` module to test. This ends up with failing with the message below (e.g. https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/60990/consoleFull): ``` Error: unrecognized module 'root'. Supported modules: pyspark-core, pyspark-sql, pyspark-streaming, pyspark-ml, pyspark-mllib ``` ## How was this patch tested? N/A Author: hyukjinkwon <[email protected]> Closes apache#13845 from HyukjinKwon/fix-build-1.6. (cherry picked from commit 4a67541)
|
Test build #61336 has finished for PR 13806 at commit
|
|
Test build #61337 has finished for PR 13806 at commit
|
|
retest this please |
|
Test build #61352 has finished for PR 13806 at commit
|
|
Hm... am I doing something wrong here? |
|
retest this please |
|
Test build #61353 has finished for PR 13806 at commit
|
|
Again, I think the error message is not related with this change. I will retest this and meanwhile try to build in my local. |
|
retest this please |
|
Test build #61356 has finished for PR 13806 at commit
|
|
Test build #61357 has finished for PR 13806 at commit
|
|
retest this please |
|
Test build #61367 has finished for PR 13806 at commit
|
|
retest this please |
|
Test build #61368 has finished for PR 13806 at commit
|
|
retest this please |
|
Test build #61370 has finished for PR 13806 at commit
|
|
retest this please |
|
Test build #61375 has finished for PR 13806 at commit
|
|
@JoshRosen finally I got passed! |
|
Merging. Thanks! Can you close this? |
…n NewHadoopRDD to branch 1.6 ## What changes were proposed in this pull request? This PR backports #13759. (`SqlNewHadoopRDDState` was renamed to `InputFileNameHolder` and `spark` API does not exist in branch 1.6) ## How was this patch tested? Unit tests in `ColumnExpressionSuite`. Author: hyukjinkwon <[email protected]> Closes #13806 from HyukjinKwon/backport-SPARK-16044.
…n NewHadoopRDD to branch 1.6 ## What changes were proposed in this pull request? This PR backports apache#13759. (`SqlNewHadoopRDDState` was renamed to `InputFileNameHolder` and `spark` API does not exist in branch 1.6) ## How was this patch tested? Unit tests in `ColumnExpressionSuite`. Author: hyukjinkwon <[email protected]> Closes apache#13806 from HyukjinKwon/backport-SPARK-16044. (cherry picked from commit 1ac830a)
What changes were proposed in this pull request?
This PR backports #13759.
(
SqlNewHadoopRDDStatewas renamed toInputFileNameHolderandsparkAPI does not exist in branch 1.6)How was this patch tested?
Unit tests in
ColumnExpressionSuite.