-
Notifications
You must be signed in to change notification settings - Fork 421
fix(idempotency): revert dict mutation that impacted static_pk_value feature #1970
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
fix(idempotency): revert dict mutation that impacted static_pk_value feature #1970
Conversation
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## develop #1970 +/- ##
===========================================
+ Coverage 97.43% 97.44% +0.01%
===========================================
Files 146 146
Lines 6660 6660
Branches 478 478
===========================================
+ Hits 6489 6490 +1
Misses 134 134
+ Partials 37 36 -1
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have the power, but FWIW, Approved. 😄
Added co-authorship to the merge commit but as your email isn't public the no-reply might not credit it correctly (I'll do in the release regardless) |
Issue number: #1968
Summary
Changes
Reverts a regression added in #1899 when making DynamoDB client thread-safe.
static_pk_value
is used by customers using Single Table design pattern with DynamoDB, where a composite key is used with a static value for its "primary key" attr. This change reverts a dictionary mutation that discarded the value fromstatic_pk_value
and usedkey_id
instead.In simple terms, same effect as:
User experience
Checklist
If your change doesn't seem to apply, please leave them unchecked.
Is this a breaking change?
RFC issue number:
Checklist:
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.