diff options
| author | Wenchen Fan <wenchen@databricks.com> | 2016-06-03 14:26:24 -0700 |
|---|---|---|
| committer | Cheng Lian <lian@databricks.com> | 2016-06-03 14:26:24 -0700 |
| commit | 61b80d552aafb262b5f817f7bc9c0acd0328715b (patch) | |
| tree | 3dd555bc0075030c8f75ae75052c7fe355aae5f9 /core/src | |
| parent | eb10b481ca51a3e010c168a1fb0baf1a94dcadfa (diff) | |
| download | spark-61b80d552aafb262b5f817f7bc9c0acd0328715b.tar.gz spark-61b80d552aafb262b5f817f7bc9c0acd0328715b.tar.bz2 spark-61b80d552aafb262b5f817f7bc9c0acd0328715b.zip | |
[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`
Author: Wenchen Fan <wenchen@databricks.com>
Closes #13474 from cloud-fan/ordinal-check.
Diffstat (limited to 'core/src')
0 files changed, 0 insertions, 0 deletions