You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(Timestamp(TimeUnit::Nanosecond,None),Null | Timestamp(_,None) | Date32 | Utf8 | LargeUtf8,) => Some(type_into.clone()),(Interval(_),Utf8 | LargeUtf8) => Some(type_into.clone()),// We can go into a Utf8View from a Utf8 or LargeUtf8(Utf8View,Utf8 | LargeUtf8 | Null) => Some(type_into.clone()),// Any type can be coerced into strings(Utf8 | LargeUtf8, _) => Some(type_into.clone()),
I can't see a reason why right now that timestamp or interval should not be a target for Utf8View. As well, there shouldn't be a reason why any type can't be coerced into Utf8View.
To Reproduce
No response
Expected behavior
Utf8View is supported as a source for coercion for Timestamp and Interval, and as a target for coercion for all types.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
datafusion/datafusion/expr/src/type_coercion/functions.rs
Line 762 in 382ba2b
I can't see a reason why right now that timestamp or interval should not be a target for Utf8View. As well, there shouldn't be a reason why any type can't be coerced into Utf8View.
To Reproduce
No response
Expected behavior
Utf8View is supported as a source for coercion for Timestamp and Interval, and as a target for coercion for all types.
Additional context
No response
The text was updated successfully, but these errors were encountered: