Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: ability to update Materialize workflow with new reference tables #17559

Open
wiebeytec opened this issue Jan 16, 2025 · 0 comments

Comments

@wiebeytec
Copy link

Feature Description

With Vitess 21, one can do:

./vtctldclient Materialize create \
  --workflow "copy_reference_tables" \
  --target-keyspace "$keyspace" \
  --source-keyspace "$source_keyspace" \
  --reference-tables "table1,table2,table3"

(or one can use the Vitess 20 and older method --table-settings <json>)

This uses one VStreams for all reference tables.

It would be great to be able to modify/update this workflow and add tables to it.

Use Case(s)

Use case in short: save load by not adding VStreams per newly created reference tables.

When developers make new tables that need to be present as reference tables, each extra (group of) table(s) adds a VStream. Especially if the source keyspace gets many changes, this can add considirable load. Being able to prevent this would be great.

@wiebeytec wiebeytec added the Needs Triage This issue needs to be correctly labelled and triaged label Jan 16, 2025
@mattlord mattlord added Type: Feature Component: VReplication and removed Needs Triage This issue needs to be correctly labelled and triaged labels Jan 16, 2025
@github-project-automation github-project-automation bot moved this to Backlog in VReplication Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

2 participants