-
Notifications
You must be signed in to change notification settings - Fork 7k
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
Unsupported type Nullable(Date) when trying to load range_hash MySQL dictionary #3284
Comments
Same problem with ODBC(Postgres) dictionaries |
Probably this ability (nullable types for range_min range_max at backend) was removed with #2093 (it was released in 18.12.17) I suggest to try workaround and cast to notnull type using view (mysql/pg), though it will break index access. |
The schema of my dictionary follows. Which of the fields is nullable type? How can they be done not nullable...?
|
check this, range_hashed does not work with any type Received exception from server (version 18.14.6): Code: 50. DB::Exception: Received from localhost:9000, ::1. DB::Exception: Unsupported type Nullable(UInt64). Code: 50. DB::Exception: Received from localhost:9000, ::1. DB::Exception: Unsupported type Nullable(Date). Seems the problem with mysql and at least postgressql. Http works fine. |
Broken after #3123 |
Fixed in master. |
Upgraded to 8.12, and my external
range_hash
dictionary that loads data from MYSQL stopped working.Error message is:
Unsupported type Nullable(Date)
.Downgraded to 8.6 and it works fine. Because did not have time to dig further could not try any other versions, just semi-randomly selected 18.6 after going over some change logs.
The text was updated successfully, but these errors were encountered: