[SPARK-34059][SQL][CORE][3.0] Use for/foreach rather than map to make sure execute it eagerly #31138
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… sure execute it eagerly
Member
Author
|
Kubernetes integration test starting |
|
Kubernetes integration test status success |
viirya
approved these changes
Jan 12, 2021
Member
Author
|
Thanks. Merged to branch-3.0. |
HyukjinKwon
added a commit
that referenced
this pull request
Jan 12, 2021
… sure execute it eagerly ### What changes were proposed in this pull request? This is a backport of #31110. I ran intelliJ inspection again in this branch. This PR is basically a followup of #14332. Calling `map` alone might leave it not executed due to lazy evaluation, e.g.) ``` scala> val foo = Seq(1,2,3) foo: Seq[Int] = List(1, 2, 3) scala> foo.map(println) 1 2 3 res0: Seq[Unit] = List((), (), ()) scala> foo.view.map(println) res1: scala.collection.SeqView[Unit,Seq[_]] = SeqViewM(...) scala> foo.view.foreach(println) 1 2 3 ``` We should better use `foreach` to make sure it's executed where the output is unused or `Unit`. ### Why are the changes needed? To prevent the potential issues by not executing `map`. ### Does this PR introduce _any_ user-facing change? No, the current codes look not causing any problem for now. ### How was this patch tested? I found these item by running IntelliJ inspection, double checked one by one, and fixed them. These should be all instances across the codebase ideally. Closes #31138 from HyukjinKwon/SPARK-34059-3.0. Authored-by: HyukjinKwon <gurwls223@apache.org> Signed-off-by: HyukjinKwon <gurwls223@apache.org>
|
Test build #133951 has finished for PR 31138 at commit
|
Contributor
|
+1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
This is a backport of #31110. I ran intelliJ inspection again in this branch.
This PR is basically a followup of #14332.
Calling
mapalone might leave it not executed due to lazy evaluation, e.g.)We should better use
foreachto make sure it's executed where the output is unused orUnit.Why are the changes needed?
To prevent the potential issues by not executing
map.Does this PR introduce any user-facing change?
No, the current codes look not causing any problem for now.
How was this patch tested?
I found these item by running IntelliJ inspection, double checked one by one, and fixed them. These should be all instances across the codebase ideally.