Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/12952#issuecomment-217930559
Making `Dataset.schema` conform to `Dataset.resolvedTEncoder.schema`
introduced multiple regression. Seems that Spark 2.0 implicitly assumes that
`Dataset.resolvedTEncoder.schema` is consistent with
`Dataset.logicalPlan.schema`. However, they don't. These two may differ in
column ordering (either top-level columns or inner nested fields) and
nullability.
Trying to figure out a more consistent fix.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
