[fix](catalog) gen partition id by name #39325
Merged
Conversation
This file contains 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
|
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
|
PR approved by anyone and no changes requested. |
|
run buildall |
|
run buildall |
TPC-H: Total hot run time: 38023 ms |
TPC-DS: Total hot run time: 185357 ms |
ClickBench: Total hot run time: 30.97 s |
|
run buildall |
TPC-H: Total hot run time: 37266 ms |
TPC-DS: Total hot run time: 189571 ms |
ClickBench: Total hot run time: 30.84 s |
|
run buildall |
TPC-H: Total hot run time: 38462 ms |
TPC-DS: Total hot run time: 195890 ms |
ClickBench: Total hot run time: 31.75 s |
zddr
approved these changes
Aug 19, 2024
|
PR approved by at least one committer and no changes requested. |
github-actions
bot
added
the
approved
morningman
added a commit
to morningman/doris
that referenced
this pull request
Aug 20, 2024
Followup apache#38525 Previously, we use sequence number to generate partition id of table in hive metastore. for example, there are 2 partitions: `dt=2024-10-02` and `dt=2024-10-03`, the partition id will be 0 and 1. But if a new partition being added： `dt=2024-10-01`, the partiton id will be 0, 1, and 2. You can see, before, the id `0` is for `dt=2024-10-02`, but now `0` is for `dt=2024-10-01`. This PR use catalog/db/table/partition name to generate a id for the partition, so that each partition will have unique id.
morningman
added a commit
that referenced
this pull request
Aug 20, 2024
dataroaring
pushed a commit
that referenced
this pull request
Aug 26, 2024
Followup #38525 Previously, we use sequence number to generate partition id of table in hive metastore. for example, there are 2 partitions: `dt=2024-10-02` and `dt=2024-10-03`, the partition id will be 0 and 1. But if a new partition being added： `dt=2024-10-01`, the partiton id will be 0, 1, and 2. You can see, before, the id `0` is for `dt=2024-10-02`, but now `0` is for `dt=2024-10-01`. This PR use catalog/db/table/partition name to generate a id for the partition, so that each partition will have unique id.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Followup #38525
Previously, we use sequence number to generate partition id of table in hive metastore.
for example, there are 2 partitions:
dt=2024-10-02anddt=2024-10-03, the partition id will be 0 and 1.But if a new partition being added：
dt=2024-10-01, the partiton id will be 0, 1, and 2.You can see, before, the id
0is fordt=2024-10-02, but now0is fordt=2024-10-01.This PR use catalog/db/table/partition name to generate a id for the partition,
so that each partition will have unique id.