[
https://issues.apache.org/jira/browse/FLINK-29895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yuri Gusev updated FLINK-29895:
-------------------------------
Description:
*Scope:*
* Reduce number of integration tests in favor of better unit test coverage
* Make sure we have good code coverage overall
was:
h2. Motivation
*User stories:*
As a Flink user, I’d like to use DynamoDB as sink for my data pipeline.
*Scope:*
* Implement an asynchronous sink for DynamoDB by inheriting the AsyncSinkBase
class. The implementation can for now reside in its own module in
flink-connectors.
* Implement an asynchornous sink writer for DynamoDB by extending the
AsyncSinkWriter. The implementation must deal with failed requests and retry
them using the {{requeueFailedRequestEntry}} method. If possible, the
implementation should batch multiple requests (PutRecordsRequestEntry objects)
to Firehose for increased throughput. The implemented Sink Writer will be used
by the Sink class that will be created as part of this story.
* Java / code-level docs.
* End to end testing: add tests that hits a real AWS instance. (How to best
donate resources to the Flink project to allow this to happen?)
h2. References
More details to be found
[https://cwiki.apache.org/confluence/display/FLINK/FLIP-171%3A+Async+Sink]
> Improve code coverage and integration tests for DynamoDB implementation of
> Async Sink
> -------------------------------------------------------------------------------------
>
> Key: FLINK-29895
> URL: https://issues.apache.org/jira/browse/FLINK-29895
> Project: Flink
> Issue Type: New Feature
> Components: Connectors / DynamoDB
> Reporter: Yuri Gusev
> Assignee: Yuri Gusev
> Priority: Major
> Labels: pull-request-available, stale-assigned
> Fix For: aws-connector-2.0.0
>
>
> *Scope:*
> * Reduce number of integration tests in favor of better unit test coverage
> * Make sure we have good code coverage overall
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
