replication: Always refresh location data#2705
replication: Always refresh location data#2705delthas wants to merge 2 commits intodevelopment/9.2from
Conversation
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 (0.00%) 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.2 #2705 +/- ##
===================================================
- Coverage 74.72% 74.57% -0.15%
===================================================
Files 200 200
Lines 13488 13507 +19
===================================================
- Hits 10079 10073 -6
- Misses 3399 3424 +25
Partials 10 10
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
ef65678 to
30c0317
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 10 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Issue: BB-491 Signed-off-by: Thomas Flament <thomas.flament@scality.com>
30c0317 to
4c0bd2f
Compare
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 10 out of 10 changed files in this pull request and generated 4 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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>
4c0bd2f to
7bb3963
Compare
|
Replaced by #2708 |
This is an intermediate step for later removing location data from the Kafka topic (in order to save space).
Issue: BB-491