[
https://issues.apache.org/jira/browse/KAFKA-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma updated KAFKA-3273:
-------------------------------
Description:
They should use `ConsumerRecord` and `ProducerRecord` as parameters and return
types respectively in order to avoid breaking users each time a new parameter
is added.
An additional question is whether we need to maintain compatibility with
previous releases. [~junrao] suggested that we do not, but [~ewencp] thought we
should.
Note that the KIP-31/32 change has broken compatibility for `MessageFormatter`
so we need to do _something_ for the next release.
was:
They should use `ConsumerRecord` and `ProducerRecord` as parameters and return
types respectively in order to avoid breaking clients each time a new parameter
is added.
An additional question is whether we need to maintain compatibility with
previous releases. [~junrao] suggested that we do not, but [~ewencp] thought we
should.
Note that the KIP-31/32 change has broken compatibility for `MessageFormatter`
so we need to do _something_ for the next release.
> MessageFormatter and MessageReader interfaces should be resilient to changes
> ----------------------------------------------------------------------------
>
> Key: KAFKA-3273
> URL: https://issues.apache.org/jira/browse/KAFKA-3273
> Project: Kafka
> Issue Type: Improvement
> Components: tools
> Reporter: Ismael Juma
> Assignee: Ismael Juma
> Fix For: 0.9.1.0
>
>
> They should use `ConsumerRecord` and `ProducerRecord` as parameters and
> return types respectively in order to avoid breaking users each time a new
> parameter is added.
> An additional question is whether we need to maintain compatibility with
> previous releases. [~junrao] suggested that we do not, but [~ewencp] thought
> we should.
> Note that the KIP-31/32 change has broken compatibility for
> `MessageFormatter` so we need to do _something_ for the next release.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
