feat(duplication): support duplication entry for multiple purposes #2163
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
duplication_entry
is an important struct for duplication, including per-duplicationproperties and progress info(confirmed decree) for each partition of a table. It
contains all useful info for a duplication. Therefore, it has been used in response to
query and sync:
duplications of single table;
Soon we would support a new interface to get duplications from multiple tables,
i.e.
list duplications
. It would request duplications of multiple tables, also includingper-duplication properties and progress info(confirmed decree and a new field last
committed decree). It still uses
duplication_entry
as the response to the client.Thus we add fields to
duplication_entry
to support more purposes.