-
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-1960] Refactor data expiration to TableMaintainer #2328
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #2328 +/- ##
============================================
- Coverage 52.96% 52.96% -0.01%
- Complexity 4303 4310 +7
============================================
Files 516 516
Lines 29716 29799 +83
Branches 2896 2901 +5
============================================
+ Hits 15739 15782 +43
- Misses 12699 12738 +39
- Partials 1278 1279 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
# Conflicts: # ams/server/src/main/java/com/netease/arctic/server/optimizing/maintainer/IcebergTableMaintainer.java # ams/server/src/main/java/com/netease/arctic/server/optimizing/maintainer/MixedTableMaintainer.java
ams/server/src/main/java/com/netease/arctic/server/optimizing/maintainer/MaintainStrategy.java
Outdated
Show resolved
Hide resolved
ams/server/src/main/java/com/netease/arctic/server/optimizing/maintainer/MaintainStrategy.java
Outdated
Show resolved
Hide resolved
I understand that the only difference between partition expiration in change+base and Iceberg is the calculation logic for determining which partitions need to expire. Change+base requires consideration of two tables. So, can we calculate them separately and pass the results to change and base using MixedTableMaintainer? |
...rver/src/main/java/com/netease/arctic/server/optimizing/maintainer/MixedTableMaintainer.java
Outdated
Show resolved
Hide resolved
...rver/src/main/java/com/netease/arctic/server/optimizing/maintainer/MixedTableMaintainer.java
Outdated
Show resolved
Hide resolved
...rver/src/main/java/com/netease/arctic/server/optimizing/maintainer/MixedTableMaintainer.java
Outdated
Show resolved
Hide resolved
# Conflicts: # ams/server/src/main/java/com/netease/arctic/server/optimizing/maintainer/IcebergTableMaintainer.java # ams/server/src/main/java/com/netease/arctic/server/optimizing/maintainer/MixedTableMaintainer.java # ams/server/src/main/java/com/netease/arctic/server/optimizing/maintainer/TableMaintainer.java
...rver/src/main/java/com/netease/arctic/server/optimizing/maintainer/MixedTableMaintainer.java
Show resolved
Hide resolved
...er/src/main/java/com/netease/arctic/server/optimizing/maintainer/IcebergTableMaintainer.java
Outdated
Show resolved
Hide resolved
LGTM |
…hots with optimized sequence (#2456) * [AMORO-1720] Fix Mixed Format KeyedTable expiring all the snapshots with optimized sequence (#2394) * should not expire the latest snapshot contains optimized sequence * add visible for testing * add fetchLatestNonOptimizedSnapshotTime for base store * get hive locations return the uri path * refactor codes and fix comments * improve for exclude files is empty for expring snapshots --------- Co-authored-by: ZhouJinsong <zhoujinsong0505@163.com> * revert changes introduced from #2328 --------- Co-authored-by: ZhouJinsong <zhoujinsong0505@163.com>
Why are the changes needed?
Enhance #1960.
Brief change log
How was this patch tested?
Add some test cases that check the changes thoroughly including negative and positive cases if possible
Add screenshots for manual tests if appropriate
Run test locally before making a pull request
Documentation