Customized CreateLookUpVindex to Include a Flag to Continue Vreplication After Backfill with an Owner Provided

[michaelhzh]

Description

This is PR for issue #8571 , which is to allow forces vreplication to continue after backfill with an owner being provided.

Related Issue(s)

#8571

Checklist

• Tests were added or are not required
• Documentation was added or is not required

[rohit-nayak-ps]

lgtm

[rohit-nayak-ps]

Just noting doc snippet provided by @michaelhzh for the -continue_after_copy_with_owner flag. To be added to vitess.io:

By default, when an owner is provided, the VReplication streams will stop after the Vindex backfill completes. Set this flag if you don’t want this to happen.

Uses

• When used in table migration from unsharded to sharded, it can override the default behavior of the workflow and continue the Vreplication Stream after Vindex backfill is completed. This allows Vindex to be kept up to date when the read and write still points to the original table at the unsharded keyspace, avoiding another backfill before SwitchWrites and any inconsistencies in Vindex.