You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Beam JIRA Bot (Jira)" <ji...@apache.org> on 2020/09/30 17:08:02 UTC
[jira] [Commented] (BEAM-10706) DynamoDBIO fail to write to the
same key in short consecution
[ https://issues.apache.org/jira/browse/BEAM-10706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17204883#comment-17204883 ]
Beam JIRA Bot commented on BEAM-10706:
--------------------------------------
This issue is assigned but has not received an update in 30 days so it has been labeled "stale-assigned". If you are still working on the issue, please give an update and remove the label. If you are no longer working on the issue, please unassign so someone else may work on it. In 7 days the issue will be automatically unassigned.
> DynamoDBIO fail to write to the same key in short consecution
> -------------------------------------------------------------
>
> Key: BEAM-10706
> URL: https://issues.apache.org/jira/browse/BEAM-10706
> Project: Beam
> Issue Type: Bug
> Components: io-java-aws
> Affects Versions: 2.23.0
> Reporter: Dennis Yung
> Assignee: Dennis Yung
> Priority: P2
> Labels: stale-assigned
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Internally, DynamoDBIO.Write uses the batchWriteItem method from the AWS SDK to sink items. However, there is a limitation in the AWS SDK that a call to batchWriteItem cannot contain duplicate keys.
> Currently DynamoDBIO.Write performs no key deduplication before flushing a batch, which could cause ValidationException: Provided list of item keys contains duplicates, if consecutive updates to a single key is within the batch size (currently hardcoded to be 25).
> To fix this bug, the batch of write requests need to be deduplicated before being sent to batchRequest.addRequestItemsEntry
--
This message was sent by Atlassian Jira
(v8.3.4#803005)