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.

• [x] #15983
• [ ] #15984
• [x] #14155
• [ ] #15985
• [x] #8653
• [ ] #14017

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.