-
Notifications
You must be signed in to change notification settings - Fork 298
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
[AMORO-2257] Automatically create tags on snapshots hour-level for iceberg Table Formats #2411
Merged
Merged
Changes from 13 commits
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
ce2c812
Automatically create tags on snapshots hour-level for iceberg Table F…
841dc98
Update configurations.md
huyuanfeng2018 2269615
fixed
abf96b0
spotless:apply
641d9b6
Adjust some code, add test cases
26e1923
Merge branch 'master' into amoro-2257
wangtaohz f65ffa8
Merge branch 'master' into amoro-2257
wangtaohz 10690c8
add `handleConfigChanged` and optimize `getTagTriggerTime`
c502dcf
remove period size
b81043d
Optimize the code
5223279
Merge branch 'master' into amoro-2257
huyuanfeng2018 aa63875
fix
7541b9c
Merge remote-tracking branch 'origin/amoro-2257' into amoro-2257
d851d47
Add little comment
18cdaba
Merge branch 'master' into amoro-2257
wangtaohz dc519bb
Merge branch 'master' into amoro-2257
e7d4d44
calculate tag time etc at the beginning
23a499b
Merge branch 'master' into amoro-2257
zhoujinsong 2ade179
Merge branch 'master' into amoro-2257
zhoujinsong 308d34d
Update docs/user-guides/configurations.md
zhoujinsong File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
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.
Hi, when I reviewed the code here, these three time-related variables made it difficult for me to understand. After carefully reviewing the code again, I have summarized the names and meanings of the three parameters:
And we calculated the 3 variables with the methods:
then,
However, the tag time here does not correspond to the time of the tag. It is easier for us to generate the corresponding tag name based on this tag time, but it does not accurately represent the data within the tag.
We should calculate the 3 variables like :
Then the value of the tag time is more accurate and the calculation methods are much simpler.
So I think we can make the code much easier to understand by: