[
https://issues.apache.org/jira/browse/KAFKA-6256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16304637#comment-16304637
]
Narendra Kumar commented on KAFKA-6256:
---------------------------------------
I doubt this has something to do with commit.interval.ms, the cache might be
getting flushed in between resulting partially aggregated records in output
topic. [~mjsax] what do you think, any pointers on this?
> Flaky Unit test:
> KStreamKTableJoinIntegrationTest.shouldCountClicksPerRegionWithNonZeroByteCache
> ------------------------------------------------------------------------------------------------
>
> Key: KAFKA-6256
> URL: https://issues.apache.org/jira/browse/KAFKA-6256
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 1.0.0
> Reporter: Matthias J. Sax
>
> {noformat}
> Expected: <[KeyValue(americas, 101), KeyValue(europe, 109), KeyValue(asia,
> 124)]>
> but: was <[KeyValue(europe, 13), KeyValue(asia, 25), KeyValue(americas,
> 23)]>
> at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
> at org.junit.Assert.assertThat(Assert.java:956)
> at org.junit.Assert.assertThat(Assert.java:923)
> at
> org.apache.kafka.streams.integration.KStreamKTableJoinIntegrationTest.countClicksPerRegion(KStreamKTableJoinIntegrationTest.java:301)
> at
> org.apache.kafka.streams.integration.KStreamKTableJoinIntegrationTest.shouldCountClicksPerRegionWithNonZeroByteCache(KStreamKTableJoinIntegrationTest.java:144)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
