Matthias J. Sax created KAFKA-17131:
---------------------------------------
Summary: Cleanup `ProcessorContext` an related interfaces
Key: KAFKA-17131
URL: https://issues.apache.org/jira/browse/KAFKA-17131
Project: Kafka
Issue Type: Improvement
Components: streams
Reporter: Matthias J. Sax
We did replace `Processor` and related classes with `api.Processor` et al. –
However, there is also `ProcessorContext`:
While `ProcessorContext` has a new `api.ProcessorContext` equivalent,
`ProcessorContext` is still used in other places (eg `StateStore#init`, and
`DeserializationExceptionHandler`)
Note, that we also have `api.ProcessingContext` as well as `StateStoreContext`
interfaces.
Side note: In general, `StateStore` is a very leaky abstraction, as it serves
two purposes. It's an interface to implement a custom `StateStore` and the top
level interface to access state stores inside a `Processor`, and thus, we leak
"runtime" method (like `init()` / `close()`) into `Processor` where they should
not be expose.
I might be worth to look into this, and figure out how to clean this all up.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
