[
https://issues.apache.org/jira/browse/KAFKA-3202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eno Thereska updated KAFKA-3202:
--------------------------------
Description:
The system test should cover the case that message format changes are made when
clients are producing/consuming. The message format change should not cause
client side issue.
We already cover 0.10 brokers with old producers/consumers in upgrade tests.
So, the main thing to test is a mix of 0.9 and 0.10 producers and consumers.
E.g., test1: 0.9 producer/0.10 consumer and then test2: 0.10 producer/0.9
consumer. And then, each of them: compression/no compression (like in upgrade
test). And we could probably add another dimension : topic configured with
CreateTime (default) and LogAppendTime. So, total 2x2x2 combinations (but maybe
can reduce that — eg. do LogAppendTime with compression only).
was:The system test should cover the case that message format changes are
made when clients are producing/consuming. The message format change should not
cause client side issue.
> Add system test for KIP-31 and KIP-32 - Change message format version on the
> fly
> --------------------------------------------------------------------------------
>
> Key: KAFKA-3202
> URL: https://issues.apache.org/jira/browse/KAFKA-3202
> Project: Kafka
> Issue Type: Sub-task
> Components: system tests
> Reporter: Jiangjie Qin
> Assignee: Eno Thereska
> Priority: Blocker
> Fix For: 0.10.0.0
>
>
> The system test should cover the case that message format changes are made
> when clients are producing/consuming. The message format change should not
> cause client side issue.
> We already cover 0.10 brokers with old producers/consumers in upgrade tests.
> So, the main thing to test is a mix of 0.9 and 0.10 producers and consumers.
> E.g., test1: 0.9 producer/0.10 consumer and then test2: 0.10 producer/0.9
> consumer. And then, each of them: compression/no compression (like in upgrade
> test). And we could probably add another dimension : topic configured with
> CreateTime (default) and LogAppendTime. So, total 2x2x2 combinations (but
> maybe can reduce that — eg. do LogAppendTime with compression only).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
