Closed Kerkesni closed 1 year ago
My role is to assist you with the merge of this
pull request. Please type @bert-e help
to get information
on this process, or consult the user documentation.
Status report is not available.
The Fix Version/s
in issue BB-355 contains:
Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:
8.6.2
Please check the Fix Version/s
of BB-355, or the target
branch of this pull request.
I have created the integration data for the additional destination branches.
bugfix/BB-355-support-delete-events-with-no-fulldocument-field
into
development/8.4
development/8.5
development/8.6
The following branches will NOT be impacted:
development/7.10
development/7.4
development/8.3
You can set option create_pull_requests
if you need me to create
integration pull requests in addition to integration branches, with:
@bert-e create_pull_requests
The following approvals are needed before I can proceed with the merge:
the author
2 peers
I have successfully deleted this pull request's integration branches.
I have created the integration data for the additional destination branches.
bugfix/BB-355-support-delete-events-with-no-fulldocument-field
into
development/8.4
development/8.5
development/8.6
The following branches will NOT be impacted:
development/7.10
development/7.4
development/8.3
You can set option create_pull_requests
if you need me to create
integration pull requests in addition to integration branches, with:
@bert-e create_pull_requests
The following approvals are needed before I can proceed with the merge:
the author
2 peers
/reset
I have successfully deleted this pull request's integration branches.
I have created the integration data for the additional destination branches.
bugfix/BB-355-support-delete-events-with-no-fulldocument-field
into
development/8.4
development/8.5
development/8.6
The following branches will NOT be impacted:
development/7.10
development/7.4
development/8.3
You can set option create_pull_requests
if you need me to create
integration pull requests in addition to integration branches, with:
@bert-e create_pull_requests
The following approvals are needed before I can proceed with the merge:
the author
2 peers
I have successfully deleted this pull request's integration branches.
I have created the integration data for the additional destination branches.
bugfix/BB-355-support-delete-events-with-no-fulldocument-field
into
development/8.4
development/8.5
development/8.6
The following branches will NOT be impacted:
development/7.10
development/7.4
development/8.3
You can set option create_pull_requests
if you need me to create
integration pull requests in addition to integration branches, with:
@bert-e create_pull_requests
The following approvals are needed before I can proceed with the merge:
the author
2 peers
/approve
The changeset has received all authorizations and has been added to the relevant queue(s). The queue(s) will be merged in the target development branch(es) as soon as builds have passed.
The changeset will be merged in:
:heavy_check_mark: development/8.4
:heavy_check_mark: development/8.5
:heavy_check_mark: development/8.6
The following branches will NOT be impacted:
development/7.10
development/7.4
development/8.3
There is no action required on your side. You will be notified here once the changeset has been merged. In the unlikely event that the changeset fails permanently on the queue, a member of the admin team will contact you to help resolve the matter.
IMPORTANT
Please do not attempt to modify this pull request.
If you need this pull request to be removed from the queue, please contact a member of the admin team now.
The following options are set: approve
I have successfully merged the changeset of this pull request into targetted development branches:
:heavy_check_mark: development/8.4
:heavy_check_mark: development/8.5
:heavy_check_mark: development/8.6
The following branches have NOT changed:
development/7.10
development/7.4
development/8.3
Please check the status of the associated issue BB-355.
Goodbye kerkesni.
…g consumer
Issue: BB-355
Problem: Some times oplog update events we get when using the Kafka log consumer don't have any metadata. This mostly happens when deleting the object right after the update.
The issue happens because we use the
fullDocument
field to retrieve the metadata, when reading the mongodb docs we see that the field represents a copy of the entire updated document at a point in time after the update, which means that in some cases this value can be unavailable like when deleting right after the update.Fix: Use the
updateDescription
field to get object metadata instead of fullDocument. Values fromupdateDescription
represent the exact changes that occurred to the object. It is possible to have non complete metadata in this field but this shouldn't be an issue as we update the full object each time in the mongoClient. One key updates like we do in the update we perform before each deletion will be ignored as we don't even have thevalue
field that's supposed to contain the metadata.