Feature Request: Improve usability of LookupVindex command

[mattlord]

Feature Description

The following is a list of desirable improvements to the LookupVindex vtctldclient command along with known bugs.

• FeatureRequest: LookupVindex create should use an existing VIndex and Table when possible #15983
• LookupVindex create does not properly cleanup / undo state changes made when it fails to create the workflow #15984
• Feature Request: Allow setting the hashing used for lookup vindexes in CreateLookupVindex #14155
• Feature Request: LookupVindex has no internalize command (equivalent to ReverseTraffic) #15985
• CreateLookupVindex against a table where lookup column is the "last" column in the table fails #8653
• Feature Request: CreateLookupVindex for multiple lookup tables #14017
• Feature Request: LookupVindex: Warn or error on target table DDL w/o appropriate index(es) #16556

Use Case(s)

Managing many lookup vindexes in Vitess.

[maxenglander]

If a previous CreateLookupVindex workflow still exists when creating a new one then you get an error that a frozen workflow exists.

I am able to issue multiple CreateLookupVindex one after another without issue. After creating them and running Workflow <workflow_id> Show, they all show as running without error. I can then "complete" them via ExternalizeVindex one after the other, and that produces the desired effect (delete VReplication streams, remove write_only param) as well.

Also, not sure what causes a CreateLookupVindex workflow to go into frozen state. I only know about creating them, letting them run, and then deleting them via ExternalizeVindex.

[mattlord]

Thanks, @maxenglander ! That list may be outdated, I'm not sure. I was starting with an aggregated list of things that I've seen reported. There may be more to at least some of them.