-
Notifications
You must be signed in to change notification settings - Fork 638
Add concurrent tiering updates to OLAP scenario test #8262
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
Add concurrent tiering updates to OLAP scenario test #8262
Conversation
swalrus1
commented
Aug 26, 2024
•
edited
Loading
edited
- add retries in the test to handle failures on nemesis cluster
- update many tables on the same store in parallel
- add ADD COLUMN, DROP COLUMN workload
- validate that eviction occur
⚪
🟢 |
⚪ ⚪
⚪
🟢 |
⚪
🟢 |
⚪ ⚪
⚪
🟢 |
@@ -524,6 +550,22 @@ def get_table_rows_count(self, tablename: str, comment: str = '') -> int: | |||
result_set = self.execute_scan_query(f'SELECT count(*) FROM `{self.get_full_path(tablename)}`') | |||
return result_set.result_set.rows[0][0] | |||
|
|||
@allure.step('Describe table {path}') | |||
def describe_table(self, path: str, settings: ydb.DescribeTableSettings = None) -> List[ydb.SchemeEntry]: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
А почему лист? Для одной таблички же один результат
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Здесь вообще должен быть другой тип -- я забыл поменять) Исправил, спасибо