You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Devin Thomson (Jira)" <ji...@apache.org> on 2020/05/13 21:16:00 UTC
[jira] [Commented] (FLINK-11547) JsonMappingException in
DynamoDBStreamsSchema
[ https://issues.apache.org/jira/browse/FLINK-11547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17106674#comment-17106674 ]
Devin Thomson commented on FLINK-11547:
---------------------------------------
[~jiaweiwu] I almost forgot about this ticket! Glad to see I'm not the only one with the issue. I will submit a PR by the end of Q2 (when we're more actively working on Flink in my team).
> JsonMappingException in DynamoDBStreamsSchema
> ---------------------------------------------
>
> Key: FLINK-11547
> URL: https://issues.apache.org/jira/browse/FLINK-11547
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kinesis
> Affects Versions: 1.8.0
> Reporter: Devin Thomson
> Priority: Major
> Attachments: full_flink_trace.txt
>
>
> If DynamoDBStreamsSchema is used as the deserializer for FlinkDynamoDBStreamsConsumer, an exception occurs during deserialization of a record. The stack trace is attached.
>
> This is a blocker for using DynamoDBStreamsSchema, but can be worked around by implementing a custom deserializer. The issue appears to be due to the usage of vanilla ObjectMapper:
>
> {code:java}
> private static final ObjectMapper MAPPER = new ObjectMapper();
> {code}
> When it should be using the appropriate mix-ins offered by the dynamodb stream adapter library:
> {code:java}
> private static final ObjectMapper MAPPER = new RecordObjectMapper();
> {code}
> This appears to resolve the issue, I tested by using my own deserializer implementation.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)