vindexes: ignore_nulls option for lookups#6222
vindexes: ignore_nulls option for lookups#6222harshit-gangal merged 1 commit intovitessio:masterfrom
Conversation
Fixes vitessio#6147 Signed-off-by: Sugu Sougoumarane <ssougou@gmail.com>
|
@sougou, @harshit-gangal - thank you! i'm not very familiar with vitess internal flow, yet, looking the method names in does this change cover the case when an existing non-null (key) column gets updated to a i'd imagine a change to |
|
fyi: our existing test case (which inserts rows with works fine with |
|
also, it might be worth changing the |
This should be fine because Update is implemented as a Delete->Create. This is because the lookup row can move across shards on an update: https://github.com/vitessio/vitess/blob/master/go/vt/vtgate/vindexes/lookup_internal.go#L279-L284
This is a breaking change. But I suspect many users may actually be misled because they expect the wrong behavior. Them switching to use
This is a limitation of the vindex design. It only accepts strings. as input values. |
Fixes #6147
Signed-off-by: Sugu Sougoumarane ssougou@gmail.com