Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15035
Shouldn't we change the reading path for Parquet rather than changing the
target row to avoid per-record type dispatch? Also, it seems a Parquet specific
issue but I wonder making changes in row is a good approach.
I remember my PR to support upcasting in schema for Parquet,
https://github.com/apache/spark/pull/14215 which I decided to close for a
better approach.
I haven't taken a look so closely but I will and leave some comments.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
