[
https://issues.apache.org/jira/browse/FLINK-13586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16900841#comment-16900841
]
Aljoscha Krettek commented on FLINK-13586:
------------------------------------------
I think we first need to discuss whether this is breaking backwards
compatibility. Going down this possible rabbit hole, where code that is
internally used by public code has to be considered we could get into
complicated territory.
> 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)
