Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/21736
@MaxGekk If we call `SQLConf.get.legacySizeOfNull` directly in the
execution path, we can update the result for an existing df, but not always. If
the physical plan of the df is also materiazed, then the generated code is
fixed and the updated config values can't be respected.
Regarding the `@transient lazy val`, if it doesn't have much benefit, shall
we just remove it for simplicity?
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
