-
Notifications
You must be signed in to change notification settings - Fork 198
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
Minibatch dynamodb client #652
Conversation
cf40593
to
45f9a09
Compare
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! do you want #664 merged and rebase this one on master?
KeyType: types.KeyTypeHash, | ||
}, | ||
{ | ||
AttributeName: aws.String("CreatedAt"), |
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.
Would this index records that don't have CreatedAt
attribute?
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.
No. All items indexed by a GSI must have values for the attributes that are part of the GSI's key schema. If we had used CreatedAt
(as opposed to RequestedAt
) for DispersalRequest, DispersalRequests still would not have been included in the GSI because DispersalRequest does not define BatchStatus
pls do. I just approved |
Replace DispersalRequest.OperatorID field with raw byte array def so that dynamo can use unmarshalMap
Convert PK to BatchID Adds custom minibatch struct conversion for batch, minibatch, dispersalRequest, dispersalResponse
Add remaining minibatch store functions
Remove blobMetadataIndex
Add unique constraint on (batchID,BATCH#batchID)
b6deafb
to
4551c2a
Compare
Why are these changes needed?
Minibatch dynamodb client
Schema uses single table design
Checks