You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Guozhang Wang (JIRA)" <ji...@apache.org> on 2016/11/16 20:46:59 UTC

[jira] [Resolved] (KAFKA-4359) Streams integration tests should not use commit interval of 1

     [ https://issues.apache.org/jira/browse/KAFKA-4359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Guozhang Wang resolved KAFKA-4359.
----------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 0.10.1.1)
                   0.10.2.0

Issue resolved by pull request 2124
[https://github.com/apache/kafka/pull/2124]

> Streams integration tests should not use commit interval of 1
> -------------------------------------------------------------
>
>                 Key: KAFKA-4359
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4359
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>    Affects Versions: 0.10.1.1
>            Reporter: Eno Thereska
>            Assignee: Eno Thereska
>             Fix For: 0.10.2.0
>
>
> Several streams integration tests use two cache sizes, 0 and 10MB. However, when they use 10MB, they still use a very small commit interval (1ms). That leads to two problems:1) a small commit interval often has the same effect as having the cache size be 0, and 2) a small commit interval is not exactly the same as the cache size being 0 and in some cases there is deduplication. This leads to the tests failing, since they don't expect deduplication.
> To solve this issue, look at KStreamAggregationDedupIntegrationTest and KStreamAggregationIntegrationTest. If you want to test dedup, it would be necessary to create another file. 
> Several tests need this cleanup.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)