[ https://issues.apache.org/jira/browse/FLINK-5013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15647147#comment-15647147 ]
Fabian Hueske commented on FLINK-5013: -------------------------------------- This might also be cause by using the wrong Maven version (3.3.x instead of 3.0.3). I've seen these {{NoSuchMethodError}}s for the {{HttpConnectionParams}} before when using a custom Flink build on EMR (although not using Kinesis but reading files from S3). > Flink Kinesis connector doesn't work on old EMR versions > -------------------------------------------------------- > > Key: FLINK-5013 > URL: https://issues.apache.org/jira/browse/FLINK-5013 > Project: Flink > Issue Type: Bug > Components: Kinesis Connector > Reporter: Robert Metzger > Priority: Critical > > A user reported on the mailing list that our Kinesis connector doesn't work > with EMR 4.4.0: > http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Kinesis-Connector-Dependency-Problems-td9790.html > The problem seems to be that Flink is loading older libraries from the "YARN > container classpath", which on EMR contains the default Amazon libraries. > We should try to shade kinesis and its amazon dependencies into a different > namespace. -- This message was sent by Atlassian JIRA (v6.3.4#6332)