[
https://issues.apache.org/jira/browse/FLINK-6951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16056911#comment-16056911
]
ASF GitHub Bot commented on FLINK-6951:
---------------------------------------
Github user tzulitai commented on the issue:
https://github.com/apache/flink/pull/4150
Thanks for the PR @bowenli86.
However, I'm not entirely sure the original version in the doc count as
"outdated".
For example, would the original versions work if you're not using the
Kinesis connector?
Or, if we decide to bump the `aws-java-sdk` version in the Kinesis
connector, would these httpcomponent versions need to correspond to?
I'm wondering if it actually makes sense to shade the httpcomponent
dependencies in the Kinesis connector, so that it doesn't incorrectly pick up
other versions in the classpath?
> Incompatible versions of httpcomponents jars for Flink kinesis connector
> ------------------------------------------------------------------------
>
> Key: FLINK-6951
> URL: https://issues.apache.org/jira/browse/FLINK-6951
> Project: Flink
> Issue Type: Bug
> Components: Kinesis Connector
> Affects Versions: 1.3.0
> Reporter: Ted Yu
> Assignee: Bowen Li
>
> In the following thread, Bowen reported incompatible versions of
> httpcomponents jars for Flink kinesis connector :
> http://search-hadoop.com/m/Flink/VkLeQN2m5EySpb1?subj=Re+Incompatible+Apache+Http+lib+in+Flink+kinesis+connector
> We should find a solution such that users don't have to change dependency
> version(s) themselves when building Flink kinesis connector.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
