[jira] [Resolved] (KAFKA-13117) After processors, migrate TupleForwarder and CacheFlushListener

["Jorge Esteban Quilcate Otoya (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KAFKA-13117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jorge Esteban Quilcate Otoya resolved KAFKA-13117.
--------------------------------------------------
    Resolution: Fixed

[https://github.com/apache/kafka/pull/11481]

> After processors, migrate TupleForwarder and CacheFlushListener
> ---------------------------------------------------------------
>
>                 Key: KAFKA-13117
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13117
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: John Roesler
>            Assignee: Jorge Esteban Quilcate Otoya
>            Priority: Major
>
> Currently, both of these interfaces take plain values in combination with timestamps:
> CacheFlushListener:
> {code:java}
> void apply(K key, V newValue, V oldValue, long timestamp)
> {code}
> TimestampedTupleForwarder
> {code:java}
>  void maybeForward(K key,
>                    V newValue,
>                    V oldValue,
>                    long timestamp){code}
> These are internally translated to the new PAPI, but after the processors are migrated, there won't be a need to have this translation. We should update both of these APIs to just accept {{Record<K, Change<V>>}}.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)