[
https://issues.apache.org/jira/browse/FLINK-13586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16900965#comment-16900965
]
Gaël Renoux commented on FLINK-13586:
-------------------------------------
[~aljoscha] As far as I know, the Flink connectors are maintained by the Flink
team as well, am I wrong ? If this is the case, it's not exactly being used by
public code as much as having a compatibility problem with another part of
Flink, which is packaged with existing jobs. From an outside point of view, I'm
using the connectors as intended, and trying to update the server to 1.8.1
broke existing jobs. It's pretty harsh for a patch version.
> Method ClosureCleaner.clean broke backward compatibility between 1.8.0 and
> 1.8.1
> --------------------------------------------------------------------------------
>
> Key: FLINK-13586
> URL: https://issues.apache.org/jira/browse/FLINK-13586
> Project: Flink
> Issue Type: Bug
> Affects Versions: 1.8.1
> Reporter: Gaël Renoux
> Priority: Major
>
> Method clean in org.apache.flink.api.java.ClosureCleaner received a new
> parameter in Flink 1.8.1. This class is noted as internal, but is used in the
> Kafka connectors (in
> org.apache.flink.streaming.connectors.kafka.FlinkKafkaProducerBase).
> The Kafka connectors library is not provided by the server, and must be set
> up as a dependency with compile scope (see
> https://ci.apache.org/projects/flink/flink-docs-stable/dev/connectors/kafka.html#usage,
> or the Maven project template). Any project using those connectors and built
> with 1.8.0 cannot be deployed on a 1.8.1 Flink server, because it would
> target the old method.
> => This methods needs a fallback with the original two arguments (setting a
> default value of RECURSIVE for the level argument).
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
