[DynamicPartition] Support specifying hot data partition#5877
Merged
morningman merged 3 commits intoapache:masterfrom May 26, 2021
Merged
[DynamicPartition] Support specifying hot data partition#5877morningman merged 3 commits intoapache:masterfrom
morningman merged 3 commits intoapache:masterfrom
Conversation
morningman
added
the
kind/feature
morningman
force-pushed
the
dynamic_storage_medium
branch
from
69801dc to
70e30a0
Compare
qidaye
reviewed
May 25, 2021
|
|
||
| * `dynamic_partition.hot_partition_num` | ||
|
|
||
| Specify how many of the latest partitions are hot partitions. For hot partition, the system will automatically set its `storage_medium` parameter to SSD, and set `storage_cooldown_time`. Assuming that the partition is divided by day and the parameter is set to 2, then the partitions of the last 2 days, `storage_medium` are all SSDs. The `storage_cooldown_time` of yesterday's partition is 0 o'clock tomorrow, and the `storage_cooldown_time` of today's partition is 0 o'clock the day after tomorrow. |
Contributor
There was a problem hiding this comment.
Would it be better to point out that the latest partition is the current partition rather than dynamic_partition.end partition?
Contributor
Author
There was a problem hiding this comment.
OK, I use a case to explain it more clear
Contributor
|
LGTM |
qidaye
approved these changes
May 25, 2021
stdpain
pushed a commit
to stdpain/incubator-doris
that referenced
this pull request
Jul 8, 2021
In some scenarios, when users use dynamic partitions, they hope to use Doris' hierarchical storage function at the same time. For example, for the dynamic partition rule of partitioning by day, we hope that the partitions of the last 3 days are stored on the SSD storage medium and automatically migrated to the HDD storage medium after expiration. This CL add a new dynamic partition property: "hot_partition_num". This parameter is used to specify how many recent partitions need to be stored on the SSD storage medium.
Closed
Hastyshell
pushed a commit
to Hastyshell/doris
that referenced
this pull request
Dec 29, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Proposed changes
In some scenarios, when users use dynamic partitions, they hope to use Doris' hierarchical storage
function at the same time.
For example, for the dynamic partition rule of partitioning by day, we hope that the partitions of the last 3 days
are stored on the SSD storage medium and automatically migrated to the HDD storage medium after expiration.
This CL add a new dynamic partition property: "hot_partition_num".
This parameter is used to specify how many recent partitions need to be stored on the SSD storage medium.
Types of changes
What types of changes does your code introduce to Doris?
Put an
xin the boxes that applyChecklist
Put an
xin the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...