viirya commented on code in PR #43694:
URL: https://github.com/apache/spark/pull/43694#discussion_r1384455469
##########
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/Cast.scala:
##########
@@ -785,17 +786,19 @@ case class Cast(
buildCast[Boolean](_, b => if (b) 1 else 0)
case DateType =>
buildCast[Int](_, d => null)
- case TimestampType if ansiEnabled =>
+ case TimestampType =>
buildCast[Long](_, t => {
val longValue = timestampToLong(t)
if (longValue == longValue.toInt) {
longValue.toInt
} else {
- throw QueryExecutionErrors.castingCauseOverflowError(t, from,
IntegerType)
+ if (ansiEnabled) {
+ throw QueryExecutionErrors.castingCauseOverflowError(t, from,
IntegerType)
+ } else {
+ null
+ }
Review Comment:
As far as I can check, it is current behavior at the beginning (at least in
8 yrs ago commits it is already this behavior). So that's why I wonder if I
miss anything. But indeed, it might be rare to cast timestamp to
byte/short/int. Maybe it is why this is not caught? 🤔
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
