Allow partialFilterExpression in backbeat index add payload - #6274
Conversation
Hello maeldonn,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Incorrect fix versionThe
Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:
Please check the |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files
... and 1 file with indirect coverage changes @@ Coverage Diff @@
## development/9.4 #6274 +/- ##
===================================================
- Coverage 86.50% 86.45% -0.05%
===================================================
Files 212 212
Lines 14579 14579
===================================================
- Hits 12611 12604 -7
- Misses 1968 1975 +7
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 |
delthas
left a comment
delthas
left a comment
There was a problem hiding this comment.
Oh wow, good catch 😅 Thanks!
d80bc44 to
3aeaede
Compare
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
Since BB-773 (backbeat 9.4.1) the lifecycle conductor sends index specs with a partialFilterExpression, rejected as an unknown field by the Joi schema of POST /_/backbeat/index?operation=add. The v2 lifecycle indexes were never created. Allow the field and add route-level tests. Issue: CLDSRV-991
3aeaede to
8f164d5
Compare
|
/approve |
Integration data createdI have created the integration data for the additional destination branches.
The following branches will NOT be impacted:
You can set option The following options are set: approve |
In the queueThe changeset has received all authorizations and has been added to the The changeset will be merged in:
The following branches will NOT be impacted:
This pull request does not target the following hotfix branch(es) so they
There is no action required on your side. You will be notified here once 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 The following options are set: approve |
|
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue CLDSRV-991. Goodbye maeldonn. |
5 participants
Since BB-773 (backbeat >= 9.4.1) the lifecycle conductor sends its v2 index
specs with a
partialFilterExpression, rejected as an unknown field by theJoi schema of
POST /_/backbeat/index?operation=add. The v2 lifecycleindexes were never created and buckets fell back to v1 listings (BB-866).
Declare the field as an optional object (the rest of the chain already
forwarded it to MongoDB) and add route-level tests.
Issue: CLDSRV-991