[
https://issues.apache.org/jira/browse/KAFKA-17178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17908661#comment-17908661
]
A. Sophie Blee-Goldman commented on KAFKA-17178:
------------------------------------------------
This is essentially just an extension of these KIPS which laid the groundwork
but apparently didn't cover the corresponding KTable APIs:
1. [KIP-478 - Strongly typed Processor
API|https://cwiki.apache.org/confluence/display/KAFKA/KIP-478+-+Strongly+typed+Processor+API]
2. [KIP-820: Extend KStream process with new Processor
API|https://cwiki.apache.org/confluence/display/KAFKA/KIP-820%3A+Extend+KStream+process+with+new+Processor+API]
> Update KTable.transformValues to new Processor API
> --------------------------------------------------
>
> Key: KAFKA-17178
> URL: https://issues.apache.org/jira/browse/KAFKA-17178
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: Matthias J. Sax
> Assignee: A. Sophie Blee-Goldman
> Priority: Major
> Labels: need-kip
> Fix For: 4.1.0
>
>
> The original Processor API was replace by a type-safe version using `Record`
> instead of K/V pairs. The old PAPI is already mainly deprecated and will be
> remove to large parts in 4.0 release.
> However, `KTable.transformValues` is still using the old PAPI, and should be
> updated to use the new `api.FixedKeyProcessor` instead of the old
> `ValueTransformerWithKey`.
> The method `transformValues` should be deprecated and replaced with
> `processValues` to `KTable.processValues`.
> At the same time, the old interfaces `ValueTransformerWithKey` and
> `ValueTransfromerWithKeySupplier` should be deprecated.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
