Optimize oplog size by stripping locations of large objects#2708
Optimize oplog size by stripping locations of large objects#2708delthas wants to merge 2 commits intodevelopment/9.1from
Conversation
Issue: BB-491 Signed-off-by: Thomas Flament <thomas.flament@scality.com>
Hello delthas,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Codecov Report❌ Patch coverage is
❌ Your patch status has failed because the patch coverage (33.33%) is below the target coverage (80.00%). You can increase the patch coverage or adjust the target coverage. Additional details and impacted files
@@ Coverage Diff @@
## development/9.1 #2708 +/- ##
===================================================
- Coverage 74.60% 74.51% -0.10%
===================================================
Files 201 201
Lines 13511 13532 +21
===================================================
+ Hits 10080 10083 +3
- Misses 3421 3439 +18
Partials 10 10
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
Request integration branchesWaiting for integration branch creation to be requested by the user. To request integration branches, please comment on this pull request with the following command: Alternatively, the |
c10295c to
5221329
Compare
This saves space on the Kafka side while preventing a refetch on most (small) objects. Issue: BB-491 Signed-off-by: Thomas Flament <thomas.flament@scality.com>
5221329 to
cf23d70
Compare
|
Replaced by #2709 |
Issue: BB-491