You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "John Roesler (Jira)" <ji...@apache.org> on 2020/10/10 03:05:00 UTC
[jira] [Commented] (KAFKA-10215) MockProcessorContext doesn't work
with SessionStores
[ https://issues.apache.org/jira/browse/KAFKA-10215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17211525#comment-17211525 ]
John Roesler commented on KAFKA-10215:
--------------------------------------
Note, this will be fixed for the new PAPI MockProcessorContext, at least, by [https://github.com/apache/kafka/pull/9396] .
> MockProcessorContext doesn't work with SessionStores
> ----------------------------------------------------
>
> Key: KAFKA-10215
> URL: https://issues.apache.org/jira/browse/KAFKA-10215
> Project: Kafka
> Issue Type: Bug
> Components: streams
> Reporter: John Roesler
> Assignee: John Roesler
> Priority: Major
> Fix For: 2.7.0
>
>
> The recommended pattern for testing custom Processor implementations is to use the test-utils MockProcessorContext. If a Processor implementation needs a store, the store also has to be initialized with the same context. However, the existing (in-memory and persistent) Session store implementations perform internal casts that result in class cast exceptions if you attempt to initialize them with the MockProcessorContext.
> A workaround is to instead embed the processor in an application and use the TopologyTestDriver instead.
> The fix is the same as for KAFKA-10200
--
This message was sent by Atlassian Jira
(v8.3.4#803005)