[
https://issues.apache.org/jira/browse/KAFKA-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239742#comment-16239742
]
Ismael Juma commented on KAFKA-6174:
------------------------------------
[~lindong], I think the issue is that the return type is not the same in the
base class. Since it's a generic parameter, it gets erased in the bytecode and
doesn't match.
To test you just have to compile code that calls that method with 0.11.0.x and
the run it with 1.0.0.
We should never do binary incompatible changes without a KIP, so yes, we need
to fix it and then propose a KIP for a future release if we think it's worth
it. And there should be a deprecation period, if possible.
> Investigate binary incompatibility issued in DescribeClusterOptions between
> 0.11 and 1.0
> ----------------------------------------------------------------------------------------
>
> Key: KAFKA-6174
> URL: https://issues.apache.org/jira/browse/KAFKA-6174
> Project: Kafka
> Issue Type: Bug
> Reporter: Dong Lin
> Assignee: Dong Lin
>
> From 0.11 to 1.0, we moved `DescribeClusterOptions timeoutMs(Integer
> timeoutMs)` from DescribeClusterOptions to AbstractOptions. User reports that
> code compiled against 0.11.0 fails when it is executed with 1.0 kafka-clients
> jar.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
