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
feat: implement batch_delete #157
Conversation
const RETRY: usize = 5; | ||
const MAX_ITEMS_PER_REQUEST: usize = 25; |
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.
For now, the limit of the number of items per request is taken into account, but the limit of whole data of a request (16MB) is not. Ideally this also should be taken into account but I think it's ok for the moment, because it seems to be very rare that the data size of 25 items exceeds 16MB in total.
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! Looks good :)
use ::raiden::IntoAttribute as _; | ||
use ::raiden::IntoAttrName as _; | ||
use ::raiden::DynamoDb as _; |
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.
👍
What does this change?
This PR does the following:
ConditionFilledOrWaitConjunction
to::raiden::ConditionFilledOrWaitConjunction
)IntoAttribute
,IntoAttrName
, andDynamoDb
trait at the beginning of the macro expansion2 and 3 will allow us to derive
Raiden
macro without having to import other items fromraiden
. In other words, all we will need to import to derive is justraiden::Raiden
.What can I check for bug fixes?
I added test cases to confirm batch_delete works for basic usecases.