feat: add test coverage for hot tier #71
Draft
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.
This PR adds test coverage for Hot Tier, which was added in #852. The following tests are being added:
Endpoint tests
/hottier
for standalone deployment - should fail, as hot tier is enabled only for distributed/hottier
for a stream which does not exist - should fail/hottier
for existing stream with time partition - should fail/hottier
for a stream with huge size (say 500 GB) - should fail because of validation failure, as disk usage should be below 80% of total disk space/hottier
for stream with existing hot tier - increase size, should be successful/hottier
for stream with existing hot tier - reduce size, should fail/hottier
for a stream which does not exist/hottier
for a stream which does not existLogical tests
/logstream/{logstream}/info
to get thefirst_event_at
field. Then set hot tier, wait for 2-3 mins, call GET/hottier
to get oldest entry in hot tier & assert both are equal.