Just a side remark. As a workaround it should be fine to remove the config. TopologyTestDriver will not produce duplicates anyway and is also not suitable to test EOS.
-Matthias On 4/4/18 1:26 PM, Guozhang Wang wrote: > Thanks Frederic for reporting the issue, I think it is indeed a missing > piece that can be added. > > Would you mind creating a JIRA for this issue? > > > Guozhang > > > On Wed, Apr 4, 2018 at 8:17 AM, Ted Yu <yuzhih...@gmail.com> wrote: > >> You saw the error because TopologyTestDriverTest doesn't explicitly call >> MockProducer#initTransactions(). >> >> To do that, TopologyTestDriver needs to expose such method to the >> TopologyTestDriverTest. >> >> You can log a JIRA if you think adding such capability is needed. >> >> Cheers >> >> On Wed, Apr 4, 2018 at 3:03 AM, Frederic Arno <frederica...@gmail.com> >> wrote: >> >>> Hello, >>> >>> I can't successfully test my processing application which require >>> EXACTLY_ONCE processing guarantee using the new TopologyTestDriver. I >>> always get the following exception: >>> java.lang.IllegalStateException: MockProducer hasn't been initialized >> for >>> transactions >>> >>> The tests all work fine as soon as I set PROCESSING_GUARANTEE_CONFIG to >>> AT_LEAST_ONCE. >>> >>> Am I doing something wrong? >>> >>> Kafka developpers can reproduce this by adding: >>> put(StreamsConfig.PROCESSING_GUARANTEE_CONFIG, >>> StreamsConfig.EXACTLY_ONCE); >>> >>> to line 88 of TopologyTestDriverTest: streams/test-utils/src/test/ja >>> va/org/apache/kafka/streams/TopologyTestDriverTest.java >>> >>> Thanks, Fred >>> >> > > >
signature.asc
Description: OpenPGP digital signature
