mirror of
https://github.com/scylladb/scylladb.git
synced 2026-04-21 00:50:35 +00:00
d6d20134de
This bug doesn't manifest in a visible way to the user. Adding the index to an existing table via GlobalSecondaryIndexUpdates is not supported so we don't need to consider what could happen for empty values of index range key. After the index is added the only interesting value user can set is omitting the value (null or empty are not allowed, see test_gsi_empty_value and test_gsi_null_value). In practice no matter of 'where' condition the underlaying materialized view code is skipping row updates with missing keys as per this comment: 'If one of the key columns is missing, set has_new_row = false meaning that after the update there will be no view row'. Thats why the added test passes both before and after the patch. But it's still usefull to include it to exercise those code paths. Fixes #11800