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

vstream: support default values #5736

Merged
merged 5 commits into from
Jan 20, 2020

Conversation

sougou
Copy link
Contributor

@sougou sougou commented Jan 19, 2020

This change refactors the vstream functionality into a separate file, along with its own manager.
With this change, we introduce a new special Gtid value "current", which will start the streams at the current position. If no keyspace is specified, then all keyspaces are included. If a keyspace has no shard specified, then all shards are included.

We reserve the empty Gtid value for the future to request all data, including existing rows.

Make vstreamer start from current position if the requested
position is "current". This will be supported by VStream.

Signed-off-by: Sugu Sougoumarane <ssougou@gmail.com>
Signed-off-by: Sugu Sougoumarane <ssougou@gmail.com>
We need more elaborate data structures for handling journal events.

Signed-off-by: Sugu Sougoumarane <ssougou@gmail.com>
Signed-off-by: Sugu Sougoumarane <ssougou@gmail.com>
In the future, we want to allow an empty position to mean:
"copy existing data also", just like in the case of VReplication.
So, for starting from current position, the VStream request
must specify the Gtid as "current".

Signed-off-by: Sugu Sougoumarane <ssougou@gmail.com>
@sougou sougou requested review from zmagg and deepthi January 19, 2020 03:30
Copy link
Member

@deepthi deepthi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@deepthi deepthi merged commit 1a2cddf into vitessio:master Jan 20, 2020
@sougou sougou deleted the ss-vstream-defaults branch January 21, 2020 19:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants