SuccessChanges

Summary

  1. [SPARK-26379][SS][BRANCH-2.3] Use dummy TimeZoneId to avoid (commit: a89f601a788ab6f1c89cefb1b4097444fb9847a4) (details)
Commit a89f601a788ab6f1c89cefb1b4097444fb9847a4 by dongjoon
[SPARK-26379][SS][BRANCH-2.3] Use dummy TimeZoneId to avoid
UnresolvedException in CurrentBatchTimestamp
## 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`.
## How was this patch tested?
Pass the Jenkins with the updated test cases.
Closes #23656 from HeartSaVioR/SPARK-26379-branch-2.3.
Lead-authored-by: Jungtaek Lim (HeartSaVioR) <kabhwan@gmail.com>
Co-authored-by: Dongjoon Hyun <dongjoon@apache.org> Signed-off-by:
Dongjoon Hyun <dongjoon@apache.org>
(commit: a89f601a788ab6f1c89cefb1b4097444fb9847a4)
The file was modifiedsql/core/src/test/scala/org/apache/spark/sql/streaming/StreamSuite.scala (diff)
The file was modifiedsql/core/src/main/scala/org/apache/spark/sql/execution/streaming/MicroBatchExecution.scala (diff)