[Feature] Implement e2e test for BanyanDB hot-warm-cold architecture #13177
Description
Search before asking
- I had searched in the issues and found no similar feature requirement.
Description
We need to introduce an e2e test case to verify the functionality of BanyanDB's hot-warm-cold architecture. This architecture manages data in different storage tiers based on its lifecycle stage, typically moving data from hot (fast, expensive storage) to warm and then to cold (slower, cheaper storage) as it ages.
- The test case requires a long-period dataset that spans multiple days or weeks to simulate data aging and migration between storage tiers.
- This dataset should be generated daily offline and made available at a remote address (e.g., a cloud storage bucket or a dedicated server).
- When the e2e test starts, it should pull the latest dataset from this remote address.
The test scenarios differ based on the repository where the e2e test is executed:
- In the SkyWalking main repository:
- Focus on verifying that queries for data at different lifecycle stages (hot, warm, cold) return the correct results.
- In the BanyanDB repository:
-
Primarily verify the data migration process between the hot, warm, and cold storage tiers.
-
Additionally, ensure that queries for data in different stages continue to work correctly after migration.
Use case
No response
Related issues
No response
Are you willing to submit a pull request to implement this on your own?
- Yes I am willing to submit a pull request on my own!
Code of Conduct
- I agree to follow this project's Code of Conduct