VReplication: Support passing VStream filters down to MySQL

[mattlord]

Description

This PR fulfills the use cases in #17681 by pushing down any valid MySQL predicates in the provided Filter to MySQL in the query used for the copy phase. This PR does NOT alter the allowed filter expressions — with the exception that it removes a limitation excluding VARCHAR columns which is no longer applicable after #9549 — but it passes those allowed predicates down to MySQL in the query used to copy the rows from the given GTID/transaction snapshot before we then proceed to stream new binlog events which also match the given filters.

Note

I will open a website PR to document the options and limitations here: https://vitess.io/docs/22.0/reference/vreplication/vstream/#filter

Related Issue(s)

• Fixes: Feature Request: Support pushing down viable VStream filters to MySQL for the copy phase #17681

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

[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 70.37037% with 8 lines in your changes missing coverage. Please review.

Project coverage is 67.75%. Comparing base (cb7d61a) to head (157497f).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
.../vt/vttablet/tabletserver/vstreamer/rowstreamer.go	70.00%	6 Missing ⚠️
.../vt/vttablet/tabletserver/vstreamer/planbuilder.go	66.66%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #17677      +/-   ##
==========================================
- Coverage   67.75%   67.75%   -0.01%     
==========================================
  Files        1587     1587              
  Lines      255780   255802      +22     
==========================================
+ Hits       173310   173323      +13     
- Misses      82470    82479       +9     

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

[mattlord]

This support was actually added here: #9549

[mattlord]

And it's tested in the new e2e test.