STAR-1133: Changes from DSEDB - DO NOT MERGE #53
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
If a user has only MODIFY permission on a table and there is a materialized view built on the same table an insert will fail with the following error: Unauthorized: Error from server: code=2100 [Unauthorized] Only base MODIFY permission is required to update base with MV. Co-authored-by: Zhao Yang <[email protected]> (cherry picked from commit 55dad39) (cherry picked from commit f1e441e) (cherry picked from commit 4c7c22c) (cherry picked from commit 68417f7)
Port of DB-1511, riptano/apollo-dtest#197 Co-authored-by: Zhao Yang <[email protected]> (cherry picked from commit c7beefc) (cherry picked from commit a02abc6) (cherry picked from commit 387d688) (cherry picked from commit d219834)
Co-authored-by: Robert Stupp <[email protected]> (cherry picked from commit 33e486a) (cherry picked from commit 9fbd1b3) (cherry picked from commit c479ab3) (cherry picked from commit 6c74210)
* STAR-432: Add tests for consistency level options Co-authored-by: Robert Stupp [email protected] (cherry picked from commit 21c18c5) (cherry picked from commit e6ae1bf) (cherry picked from commit 05b7502) (cherry picked from commit b694f07)
Co-authored-by: Aleksandr Sorokoumov <[email protected]> (cherry picked from commit fd2b1c3) (cherry picked from commit 66e6b72) (cherry picked from commit 7060130)
* STAR-765: Add tests for cloud connection. It is not possible without some infrastructre or tooling effort to trully test cloud connection. Instead added tests focus on proper cqlsh behavior when secure connect bundle is specified: - proper default consistency level - debug information - reading from cqlshrc and parameters - skipping host / port information Testing validation is based on error msgs and debug info. (cherry picked from commit 9f8cba3) (cherry picked from commit 50bf851) (cherry picked from commit e83d99a) (cherry picked from commit a7ef525)
The goal of the test is to "exercise the retry and back-off policies". And test is trying to achieve it by: - using arbitrary low write timeout - and loading / exporting / importing / exporting the data - assuming that retries and back-off will handle it. Unfortunately it is very sensitive... Because we need to find a perfect balance for the timeout and req/s, so that: - timeouts are indeed hit - and default COPY util not abort after 90s without succ write - and default COPY will not abort after 12 unsuccessull backoff attempts This change disables this test because: - there is no logic in the test that would check if indeed retries and backoff are exercised, so - it is perfectly possible that when it passes it just passes without any value - there are special tests for MAXATTEMPTS and for backoff policy Final note: mechanism of retries and backoff policy in COPY command could be improved by providing some backpressure mechanism to slowdown writes rather than doing retry or backoff exponentital (with random!). But this would be a new feature and COPY util is not a place we would like to invest. (cherry picked from commit 897aab7) (cherry picked from commit 602cf53)
Cluster stop requests in cleanup_cluster are made with "gently=True" when Jacoco code coverage is enabled to allow the jacoco agent to record results; however, some tests leave nodes in a state where this type of shutdown does not succeed, resulting in the test being marked failed regardless of it's true completion status. This change will retry these stop requests with "gently=False" so that the test completion status will not be altered due to shutdown not completing. (cherry picked from commit f6fc3d3) (cherry picked from commit aff9d6e)
…r_size_test (#41) Co-authored-by: Branimir Lambov <[email protected]> (cherry picked from commit 7777fa9) (cherry picked from commit d06d4c6)
In DB-4215 compaction has been separated from repairs and that separation seems to be pulled from DSE along with UCS. Therefore, checking for the repair status depending on whether compaction was run or not is nor relevant any longer. This commit updates the test_consistent_repair to the version we have in apollo-dtest. (cherry picked from commit b454087)
(cherry picked from commit fd2ebac)
djatnieks
reviewed
Mar 8, 2022
| @@ -0,0 +1,30 @@ | |||
| --- a/tools/assertions.py | |||
| +++ b/tools/assertions.py | |||
There was a problem hiding this comment.
Are these update-history files meant to be included?
djatnieks
approved these changes
Mar 8, 2022
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.