[
https://issues.apache.org/jira/browse/KAFKA-4556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Savdeep Singh updated KAFKA-4556:
---------------------------------
Description:
When binding builder with multiple topics, single resultant topic has unordered
set of messages.
This issue is at millisecond level. When messages with same milisecond level
are added in topics.
Scenario : (1 producer : p1 , 2 topics t1 and t2, streams pick form these 2
topics and save in resulting t3 topic, 4 partitions of t3 and 4 consumers of 4
partitions )
Case: When p1 adds messages with same millisecond timestamp into t1 and t2 .
Stream combine and form t3. When this t3 is consumed by consumer, it has
different order of same millisecond messages.
was:
When binding builder with multiple topics, single resultant topic has unordered
set of messages.
This issue is at millisecond level. When messages with same milisecond level
are added in topics.
Scenario : (1 producer : p1 , 2 topics t1 and t2, streams pick form these 2
topics and save in resulting t3 topic, 4 partitions of t3 and 4 consumers of 4
partitions )
Case: When p1 adds messages with same millisecond timestamp into t1 and t2 .
Stream combine and form
> unordered messages when multiple topics are combined in single topic through
> stream
> -----------------------------------------------------------------------------------
>
> Key: KAFKA-4556
> URL: https://issues.apache.org/jira/browse/KAFKA-4556
> Project: Kafka
> Issue Type: Bug
> Reporter: Savdeep Singh
>
> When binding builder with multiple topics, single resultant topic has
> unordered set of messages.
> This issue is at millisecond level. When messages with same milisecond level
> are added in topics.
> Scenario : (1 producer : p1 , 2 topics t1 and t2, streams pick form these 2
> topics and save in resulting t3 topic, 4 partitions of t3 and 4 consumers of
> 4 partitions )
> Case: When p1 adds messages with same millisecond timestamp into t1 and t2 .
> Stream combine and form t3. When this t3 is consumed by consumer, it has
> different order of same millisecond messages.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
