You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
DynamoDb enhanced client: support UpdateExpressions in single-request update #5554
Update expressions in the extensions are applicable for use cases where you want to do the same thing with an attribute every time that you call the database, such as atomic counters. However, if you need a one-time effect for a single request, then leveraging the extension framework isn’t useful.
Use Case
I need to atomically increment a numeric value in a table column by different amounts on demand, without first reading the current value.
Consider this table:
@Getter
@Setter
@DynamoDbBean
public class Recording {
private String id;
private Long totalRecordingSeconds;
I need to be able to update and increment the value of totalRecordingSeconds with different durations: +30, + 20 ... etc, without reading the current value.
It would be helpful to be able to perform something like:
Hi @debora-ito, my team would also like to utilize the features in this PR.
Did you get the chance to review #3836?
I see the PR hasn't been reviewed by the team, I'm not sure if this means it's abandoned or it should be refactored.
Hi @debora-ito, can you please help here with the current status of the above PR (#3836) ?
My team would really appreciate the above feature being implemented as currently we are utilizing one of the available methods to do the same which is not quite efficient & scalable & would hence want to move away from it as soon as possible.
Activity
debora-ito commentedon Sep 4, 2024
PR #3836 started working on this but it lost traction. I'll see if I can get it moving again.
IDUN-BogdanPi commentedon Sep 6, 2024
Much appreciated!
evg-tso commentedon Jan 1, 2025
Hi @debora-ito, my team would also like to utilize the features in this PR.
Did you get the chance to review #3836?
I see the PR hasn't been reviewed by the team, I'm not sure if this means it's abandoned or it should be refactored.
Ayush-10 commentedon Aug 18, 2025
Hi @debora-ito, can you please help here with the current status of the above PR (#3836) ?
My team would really appreciate the above feature being implemented as currently we are utilizing one of the available methods to do the same which is not quite efficient & scalable & would hence want to move away from it as soon as possible.