Github user mgaido91 commented on the issue:
https://github.com/apache/spark/pull/19865
@kiszk I think that in the case you hit them, this might have also been
done appositely and relying on the way Java behaves, ie. that it uses the local
variable and the global one is not used there. It can also be something which
has been designed like that. In this way instead you are forcing a behavior
which is not the expected one.
I totally agree with @cloud-fan, that we should fix the problem where they
are created, if there is any. We can also decide that such situation should be
avoided for clarity, and therefore we can change the point where you find this
behavior to be present. I am neutral to that. But I disagree in creating a
situation which is counterintuitive.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
