Allow nullable key in MergeTree#12433
Conversation
robot-clickhouse
added
doc-alert
pr-feature
|
Irrelevant failure due to test is flaky. |
alexey-milovidov
left a comment
alexey-milovidov
left a comment
There was a problem hiding this comment.
Ok.
But for full support we also have to implement IS NULL, IS NOT NULL in KeyCondition.
|
Is this feature implemented? Based on the example above I cant create the table CREATE TABLE nullable_key
(k Nullable(int), v int) ENGINE MergeTree ORDER BY k SETTINGS allow_nullable_key = 1;
Error |
|
It's available from version 20.7. |
|
你好 虽然20.7版本在create table 时解决了这个问题，但是新的MaterializeMySQL Feature是自动创建表的，如故mysql中存在索引为NULL时依然会报错 |
|
@yanchaoguo fixed in #14397 |
Which version will be merged |
20.7 |
你好 虽然20.7版本在create table 时解决了这个问题，但是新的MaterializeMySQL Feature是自动创建表的，如故mysql中存在索引为NULL时依然会报错 Upd (machine translation) : Hello. Although the 20.7 version solved this problem when creating table, the new MaterializeMySQL Feature automatically creates the table. If there is an index in mysql, it will still report an error. |
7 participants
I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Allow Nullable types as keys in MergeTree tables. #5319
Detailed description / Documentation draft:
A new setting
allow_nullable_keyis created which enables this feature. The default value isfalse.NULLs comparison order is NULLS_LAST, which is based on #8834