[
https://issues.apache.org/jira/browse/KAFKA-17131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias J. Sax updated KAFKA-17131:
------------------------------------
Labels: kip (was: needs-kip)
> Cleanup `ProcessorContext` usage
> --------------------------------
>
> Key: KAFKA-17131
> URL: https://issues.apache.org/jira/browse/KAFKA-17131
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Matthias J. Sax
> Assignee: Matthias J. Sax
> Priority: Major
> Labels: kip
>
> We did replace `Processor` and related classes with `api.Processor` et al. –
> However, there is also `ProcessorContext` which was deprecated via KIP-478
> (AK 2.7) but not marked as deprecated as it was in use in many other places.
> Many of the methods which used the old `ProcessorContext` got removed in AK
> 4.0 release, and some others are already deprecated.
> However, `ProcessorContext` is still in use in internal code, and we should
> try to refactor internal code (especially for state stores) to move off the
> old interface, so we can eventually remove it (most likely in AK 5.0).
> When we make `ProcessorContext` as deprecated, we can also mark
> `org.apache.kafka.streams.processor.To` helper class as deprecated, as it's
> only use by `ProcessorContext` (we need to do a KIP for this).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
