New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
caseWithExpression (case + toInt16OrNull) unexpected behaviour (All CH versions) #9596
Comments
Known issue: lack of proper support for Nullable in function |
I remember that I saw something similar but I cannot find the existing issue. |
The function It cannot be easily extended for proper support of Nullable, because it is implemented only for a few carefully optimized cases (num -> num, num -> string, string -> num, string -> string) but lacks the generic implementation that can work for all possible types, including Nullable. Let's note that the behaviour of (for this step, ask @amosbird (Telegram: @amosbird) or @4ertus2) The dictionary inside the function (for this step, ask @KochetovNicolai) |
Also it's a good idea to use We can convert source array elements to ColumnUnique to represent them as a dictionary to offsets in the destination array. If the types of source column and source array to transform or destination array and destination default value are different, we can convert array to We can also support non-constant destination array easily. |
@antonio2368 check this |
Fixed in 23.5. |
The text was updated successfully, but these errors were encountered: