Description
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
Attachments
Issue Links
- relates to
-
KAFKA-10200 MockProcessorContext doesn't work with WindowStores
-
- Resolved
-