Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/13811
hi @inouehrs , sorry I haven't noticed that you already have a PR for this
JIRA ticket.
Yea the root cause of this bug is exactly what you described in your PR
descption, thanks for finding this out!
However, I don't think adding a check to stop processing the children in
`TreeNode.withNewChildren` is a good fix, we are replacing the wrong children
there.
Instead, I think we should avoid mistakenly treating `MapOjects.loopVar` as
a child. Do you mind reviewing my PR at
https://github.com/apache/spark/pull/13835? thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
