[SPARK-34059][SQL][CORE][2.4] Use for/foreach rather than map to make sure execute it eagerly #31139
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
map
alone might leave it not executed due to lazy evaluation, e.g.)We should better use
foreach
to 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.