GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/13807
[SPARK-16097][SQL] Encoders.tuple should handle null object correctly
## What changes were proposed in this pull request?
Although the top level input object can not be null, but when we use
`Encoders.tuple` to combine 2 encoders, their input objects are not top level
anymore and can be null. We should handle this case.
## How was this patch tested?
new test in DatasetSuite
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cloud-fan/spark bug
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/13807.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 #13807
----
commit 45f74f624ba8774c3735896915995c4d81785884
Author: Wenchen Fan <wenc...@databricks.com>
Date: 2016-06-21T11:31:46Z
Encoders.tuple should handle null object correctly
----
---
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
