https://github.com/apache/spark
Revision 448a06375fcdae04a17006bdb2d02a2b5fccaca7 authored by Dongjoon Hyun on 27 January 2019, 18:04:51 UTC, committed by Dongjoon Hyun on 27 January 2019, 18:05:08 UTC
## What changes were proposed in this pull request?

Spark replaces `CurrentTimestamp` with `CurrentBatchTimestamp`.
However, `CurrentBatchTimestamp` is `TimeZoneAwareExpression` while `CurrentTimestamp` isn't.
Without TimeZoneId, `CurrentBatchTimestamp` becomes unresolved and raises `UnresolvedException`.

Since `CurrentDate` is `TimeZoneAwareExpression`, there is no problem with `CurrentDate`.

This PR reverts the [previous patch](https://github.com/apache/spark/pull/23609) on `MicroBatchExecution` and fixes the root cause.

## How was this patch tested?

Pass the Jenkins with the updated test cases.

Closes #23660 from dongjoon-hyun/SPARK-26379.

Authored-by: Dongjoon Hyun <dongjoon@apache.org>
Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
(cherry picked from commit 1ca6b8bc3df19503c00414e62161227725a99520)
Signed-off-by: Dongjoon Hyun <dongjoon@apache.org>
1 parent 46a9018
History
Tip revision: 448a06375fcdae04a17006bdb2d02a2b5fccaca7 authored by Dongjoon Hyun on 27 January 2019, 18:04:51 UTC
[SPARK-26379][SS][FOLLOWUP] Use dummy TimeZoneId to avoid UnresolvedException in CurrentBatchTimestamp
Tip revision: 448a063

README.md

back to top