hddong commented on a change in pull request #25389: [SPARK-28657][CORE] Fix
currentContext Instance failed sometimes
URL: https://github.com/apache/spark/pull/25389#discussion_r322041927
##########
File path: core/src/test/scala/org/apache/spark/util/UtilsSuite.scala
##########
@@ -915,6 +918,7 @@ class UtilsSuite extends SparkFunSuite with
ResetSystemProperties with Logging {
}
test("Set Spark CallerContext") {
+ SparkHadoopUtil.get.conf.setBoolean("hadoop.caller.context.enabled", true);
Review comment:
> It sounds like tests using Hadoop 2.8+ would catch this case already. We
do have a Hadoop 3.2 test job, so I wonder why it didn't trigger it.
Nevertheless, I don't think you can force this to true here, yes. Maybe it's
hard to test independently at all and so this can be removed.
ok, it will be removed.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
