-
Notifications
You must be signed in to change notification settings - Fork 588
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
tests of ttl utility functions on SS #12092
Conversation
⚪ Test history | Ya make output | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
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.
I would suggest incorporating tier index into the error messages (for example: "tier 1: missing ApplyAfterSeconds").
The user gives a sequence of tiers, and error message without accurate addressing wouldn't be that helpful (even if sequence dize is supposed to be small).
case NKikimrSchemeOp::TTTLSettings_TTier::kEvictToExternalStorage: | ||
break; | ||
case NKikimrSchemeOp::TTTLSettings_TTier::ACTION_NOT_SET: | ||
errStr = "Unset tier action"; |
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.
Message not in line with the other messages.
I would suggest "Missing Action in the tier".
errStr = "Only the last tier in TTL settings can have Delete action"; | ||
const auto& tier = ttlSettings.GetTiers(i); | ||
if (!tier.HasApplyAfterSeconds()) { | ||
errStr = "Missing ApplyAfterSeconds in a tier"; |
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.
"in the tier"
⚪ Test history | Ya make output | Test bloat
⚪ Test history | Ya make output | Test bloat | Test bloat
⚪ Test history | Ya make output | Test bloat | Test bloat | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
⚪ Test history | Ya make output | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
⚪ Test history | Ya make output | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
⚪ Test history | Ya make output | Test bloat
⚪ Test history | Ya make output | Test bloat | Test bloat
🟢
*please be aware that the difference is based on comparing your commit and the last completed build from the post-commit, check comparation |
No description provided.