[
https://issues.apache.org/jira/browse/BEAM-13209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17441194#comment-17441194
]
Alexey Romanenko edited comment on BEAM-13209 at 11/9/21, 2:29 PM:
-------------------------------------------------------------------
I'd say it's rather P1 priority since it can cause a data loss (see
[https://beam.apache.org/contribute/jira-priorities/]). P0 is more about
infrastructure outage or similar things.
was (Author: aromanenko):
I'd say it's rather P1 priority since it can cause a data loss (see
https://beam.apache.org/contribute/jira-priorities/)
> DynamoDBIO silently drops unprocessed items
> -------------------------------------------
>
> Key: BEAM-13209
> URL: https://issues.apache.org/jira/browse/BEAM-13209
> Project: Beam
> Issue Type: Bug
> Components: io-java-aws
> Reporter: Moritz Mack
> Priority: P1
> Labels: aws, data-loss, dynamodb
>
> `[batchWriteItem|https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_BatchWriteItem.html]`
> might fail partially and return unprocessed items. Such partial failures are
> not handled and result in a data loss.
> If hitting DynamoDB at scale it's rather likely to run into this.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
