forked from scylladb/scylla-cdc-rust
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Refactor tests #1
Open
Ponewor
wants to merge
24
commits into
parallelize_tests
Choose a base branch
from
refactor_tests
base: parallelize_tests
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Ponewor
force-pushed
the
parallelize_tests
branch
from
April 16, 2022 01:21
a3e948b
to
da5cdf8
Compare
Ponewor
force-pushed
the
parallelize_tests
branch
2 times, most recently
from
April 19, 2022 13:18
b8889cd
to
c2d5c4e
Compare
Parallelize tests
…ghlight its positivity
…o highlight its positivity
Check if replication went correctly after each query
Cleanup datetimes
Replicator consumer wrongly assumed that the values for original table's clustering key coming from CDC Log table are not null. However for some queries like range deletes clustering key may be unspecified. An example of such a query is: SELECT FROM table WHERE pk = 0; This would result in two rows in CDC Log table both having null as a clustering key value. As a remedy, types for clustering key values and in consequence all the other columns' values have been changed from &CqlValue to Option<&CqlValue>.
…en batch is not finished instead of false
…the last read row should not be skipped
Ponewor
force-pushed
the
refactor_tests
branch
6 times, most recently
from
April 20, 2022 16:52
a5efa25
to
cd3bf66
Compare
Ponewor
force-pushed
the
refactor_tests
branch
2 times, most recently
from
April 21, 2022 01:14
1390f9c
to
d7fd267
Compare
…tinuously Fix fetch_generations_continuously
Implement range row deletes
…emTime to chrono to make it more consistent with the rest of the library
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.