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
Use case
We have some column with very long values in it, but we want to use that column in PRIMARY KEY for faster query lookup (WHERE column = 'long_string' or WHERE column IN ('long_string1','long_string2')).
We dont want to load all this long values in ram, so we can use some deterministic function(hash, startsWith, slice) to reduce key size. Describe the solution you'd like
Add some setting and optimization which would replace WHERE column = 'long_row' with
WHERE cityHash64(column) = cityHash64('long_string') AND column = 'long_string' (if table definition contains ORDER BY (cityHash64(column))
Describe alternatives you've considered
Sometimes we can write that optimization by yourselfs, but sometimes cant.
For example if we run queries from software with query builder.
The text was updated successfully, but these errors were encountered:
Sounds reasonable. Perhaps we can have a special operator for this, like column ~ 'long_string' and some additional definitions added when creating merge tree tables.
Use case
We have some column with very long values in it, but we want to use that column in PRIMARY KEY for faster query lookup (WHERE column = 'long_string' or WHERE column IN ('long_string1','long_string2')).
We dont want to load all this long values in ram, so we can use some deterministic function(hash, startsWith, slice) to reduce key size.
Describe the solution you'd like
Add some setting and optimization which would replace WHERE column = 'long_row' with
WHERE cityHash64(column) = cityHash64('long_string') AND column = 'long_string' (if table definition contains ORDER BY (cityHash64(column))
Describe alternatives you've considered
Sometimes we can write that optimization by yourselfs, but sometimes cant.
For example if we run queries from software with query builder.
The text was updated successfully, but these errors were encountered: