Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/5141#issuecomment-86882056
Oh sorry, I thought you were just using `ParquetRelation` as an example.
Actually we're trying to replace `ParquetRelation` entirely with
`ParquetRelation2`, probably this will happen in 1.4. So in general we don't
intend to add schema evolution support for `ParquetRelation`. If you do need to
backport this to `ParquetRelation`, you may follow the approach used in #5214.
The key point is that, make sure those additional fields are nullable, as
nullability is significant in Parquet.
---
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
