LookupVindex: Multiple lookup tables support for LookupVindexCreate

[beingnoble03]

Description

Testing

LookupVindex command:

vtctldclient --server localhost:15999 LookupVindex --name "lookup_workflow1" --table-keyspace customer create --params-file="vindex_params.json"

vindex_params.json file:

{
    "keyspace": "customer",
    "vindexes": [
        {
            "name": "corder_lookup",
            "lookup_vindex_type": "consistent_lookup_unique",
            "table_owner": "corder",
            "table_owner_columns": [
                "sku"
            ]
        },
        {
            "name": "customer_lookup",
            "lookup_vindex_type": "consistent_lookup_unique",
            "table_owner": "customer",
            "table_owner_columns": [
                "email"
            ]
        }
    ],
    "tablet_types": [
        1
    ]
}

Related Issue(s)

• Feature Request: CreateLookupVindex for multiple lookup tables #14017

Checklist

• "Backport to:" labels have been added if this change should be back-ported to release branches
• If this change is to be back-ported to previous releases, a justification is included in the PR description
• Tests were added or are not required
• Did the new or modified tests pass consistently locally and on CI?
• Documentation was added or is not required

Deployment Notes

[vitess-bot]

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

• Ensure that the Pull Request has a descriptive title.
• Ensure there is a link to an issue (except for internal cleanup and flaky test fixes), new features should have an RFC that documents use cases and test cases.

Tests

• Bug fixes should have at least one unit or end-to-end test, enhancement and new features should have a sufficient number of tests.

Documentation

• Apply the release notes (needs details) label if users need to know about this change.
• New features should be documented.
• There should be some code comments as to why things are implemented the way they are.
• There should be a comment at the top of each new or modified test to explain what the test does.

New flags

• Is this flag really necessary?
• Flag names must be clear and intuitive, use dashes (-), and have a clear help text.

If a workflow is added or modified:

• Each item in Jobs should be named in order to mark it as required.
• If the workflow needs to be marked as required, the maintainer team must be notified.

Backward compatibility

• Protobuf changes should be wire-compatible.
• Changes to _vt tables and RPCs need to be backward compatible.
• RPC changes should be compatible with vitess-operator
• If a flag is removed, then it should also be removed from vitess-operator and arewefastyet, if used there.
• vtctl command output order should be stable and awk-able.

[codecov]

Codecov Report

Attention: Patch coverage is 9.85075% with 302 lines in your changes missing coverage. Please review.

Project coverage is 67.61%. Comparing base (a9d6969) to head (86d4cd9).
Report is 18 commits behind head on main.

Files with missing lines	Patch %	Lines
go/vt/vtctl/workflow/lookup_vindex.go	9.00%	202 Missing ⚠️
.../command/vreplication/lookupvindex/lookupvindex.go	1.98%	99 Missing ⚠️
go/vt/vtctl/workflow/server.go	91.66%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #17566      +/-   ##
==========================================
- Coverage   67.69%   67.61%   -0.09%     
==========================================
  Files        1584     1585       +1     
  Lines      254541   255140     +599     
==========================================
+ Hits       172315   172509     +194     
- Misses      82226    82631     +405     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[beingnoble03]

Since we will support backfilling multiple lookup tables, this unit test can be removed.