You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "PoAn Yang (Jira)" <ji...@apache.org> on 2024/12/18 00:56:00 UTC

[jira] [Commented] (KAFKA-17131) Cleanup `ProcessorContext` usage

    [ https://issues.apache.org/jira/browse/KAFKA-17131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17906570#comment-17906570 ] 

PoAn Yang commented on KAFKA-17131:
-----------------------------------

Hi [~mjsax], it looks like this Jira would like to deprecate `
org.apache.kafka.streams.processor.ProcessorContext`. If you're not working on this, may I take it? Thank you.

> 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
>            Priority: Major
>              Labels: needs-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).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)