diff options
author | windpiger <songjun@outlook.com> | 2017-02-13 12:25:13 +0100 |
---|---|---|
committer | Herman van Hovell <hvanhovell@databricks.com> | 2017-02-13 12:25:13 +0100 |
commit | 04ad822534e8ded96a9ba4b7d43320e53c6d2808 (patch) | |
tree | 82d0d202e0782587345738a1746b1cfae3327ce1 /python/MANIFEST.in | |
parent | 8f03ad547895b63825cff751265231b4fb75d660 (diff) | |
download | spark-04ad822534e8ded96a9ba4b7d43320e53c6d2808.tar.gz spark-04ad822534e8ded96a9ba4b7d43320e53c6d2808.tar.bz2 spark-04ad822534e8ded96a9ba4b7d43320e53c6d2808.zip |
[SPARK-19496][SQL] to_date udf to return null when input date is invalid
## What changes were proposed in this pull request?
Currently the udf `to_date` has different return value with an invalid date input.
```
SELECT to_date('2015-07-22', 'yyyy-dd-MM') -> return `2016-10-07`
SELECT to_date('2014-31-12') -> return null
```
As discussed in JIRA [SPARK-19496](https://issues.apache.org/jira/browse/SPARK-19496), we should return null in both situations when the input date is invalid
## How was this patch tested?
unit test added
Author: windpiger <songjun@outlook.com>
Closes #16870 from windpiger/to_date.
Diffstat (limited to 'python/MANIFEST.in')
0 files changed, 0 insertions, 0 deletions