GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/13474
[SPARK-15547][SQL] nested case class in encoder can have different number
of fields from the real schema
## What changes were proposed in this pull request?
There are 2 kinds of `GetStructField`:
1. resolved from `UnresolvedExtractValue`, and it will have a `name`
property.
2. created when we build deserializer expression for nested tuple, no
`name` property.
When we want to validate the ordinals of nested tuple, we should only catch
`GetStructField` without the name property.
## How was this patch tested?
new test in `EncoderResolutionSuite`
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cloud-fan/spark ordinal-check
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/13474.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #13474
----
commit 51b9df8b38a8d1cf4fc357de29be059157e099cb
Author: Wenchen Fan <[email protected]>
Date: 2016-06-02T21:13:42Z
nested case class in encoder can have different number of fields from the
real schema
----
---
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]
