-
Notifications
You must be signed in to change notification settings - Fork 816
Log outstanding writes in DynamoDB #734
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
Conversation
@@ -731,6 +734,7 @@ func (a storageClient) putS3Chunk(ctx context.Context, key string, buf []byte) e | |||
}) | |||
} | |||
|
|||
// Slice of values returned; map key is attribute name |
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.
Thanks for this & similar comments. What do you think about a follow-up PR replacing string
with typedefs?
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.
LGTM.
Sadly I had failed to observe it crashing very occasionally; there are entries which have a hash key and range key but no value. I have modified the code to be paranoid about all three. |
Still LGTM. |
} | ||
if valueAttr, ok := item[valueKey]; ok { | ||
value = valueAttr.B | ||
} |
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.
Feels like something that could have been statically checked for. Oh well.
To help investigate #733. From existing log lines I know we very commonly get just 1 item remaining at the timeout, so I want to know what it is.
Also some drive-by comments because I needed to figure out what was going on.