gengliangwang commented on PR #59283:
URL: https://github.com/apache/spark/pull/59283#issuecomment-6322762680
@bhollis-dbx The PR description still says "No" under "Does this PR
introduce _any_ user-facing change?", but generated column names change for
chained nested updates. The new test "chained nested field updates should use
compact generated column names" pins the new names, e.g.
```scala
col("s").withField("_1.x", lit(1)).withField("_1.y", lit(2))
// update_fields(s, WithField(update_fields(s._1, WithField(1),
WithField(2))))
```
Users who reference these auto-generated names (e.g. `df.columns`,
`col("update_fields(...)")`, or downstream table schemas written without an
alias) would be affected. Could you update the description to call out this
change with a before/after example? Thanks!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
