You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Ying Xu (JIRA)" <ji...@apache.org> on 2018/09/20 21:32:00 UTC
[jira] [Closed] (FLINK-10358) Flink kinesis connector could throw
NPE during getRecords() call
[ https://issues.apache.org/jira/browse/FLINK-10358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ying Xu closed FLINK-10358.
---------------------------
Resolution: Fixed
> Flink kinesis connector could throw NPE during getRecords() call
> -----------------------------------------------------------------
>
> Key: FLINK-10358
> URL: https://issues.apache.org/jira/browse/FLINK-10358
> Project: Flink
> Issue Type: Bug
> Components: Kinesis Connector
> Reporter: Ying Xu
> Assignee: Ying Xu
> Priority: Major
> Labels: pull-request-available
>
> When extending the flink kinesis connector to consume from a dynamodb stream, it was found NPE could be thrown at [here|https://github.com/apache/flink/blob/e3c98f05d3544d0165c2d97d2d00fcd295cef8c8/flink-connectors/flink-connector-kinesis/src/main/java/org/apache/flink/streaming/connectors/kinesis/internals/ShardConsumer.java#L376] .
> This is because the [getRecords API|https://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_streams_GetRecords.html] in dynamodb streams does not return the millisBehindLatest field and has it set to null. Null check is probably needed here.
> See FLINK-4582 for the context of building dynamodb streams connector on top of the Kinesis connector.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)