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

Stanislav Spiridonov edited comment on KAFKA-16585 at 4/22/24 4:47 PM:
-----------------------------------------------------------------------

The case is relatively simple. I have KTable with entities that have to be 
enrichment with icon attribute from side service. So, the processor maintains 
the internal store with entities keys and periodically ask the service for 
update for registered ids. If icon has changes it forward the message with new 
icon. The key of record is entity key (String), value is a icon (String).


was (Author: foal):
The case is relatively simple. I have KTable with entities that have to be 
enrichment with icon attribute from side service. So, the processor maintains 
the internal store with entities keys and periodically ask the service for 
update for registered ids. If icon has changes it forward the message with new 
icon. The key of record is entity key (String), value is a icon (String).

 

BTW I faced into strange behaviour - if I forward new record from another 
thread it arrived to incorrect processor. So now I just update store from icon 
KTable instead of forward the record.   

> No way to forward message from punctuation method in the FixedKeyProcessor
> --------------------------------------------------------------------------
>
>                 Key: KAFKA-16585
>                 URL: https://issues.apache.org/jira/browse/KAFKA-16585
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>    Affects Versions: 3.6.2
>            Reporter: Stanislav Spiridonov
>            Priority: Major
>
> The FixedKeyProcessorContext can forward only FixedKeyRecord. This class 
> doesn't have a public constructor and can be created based on existing 
> records. But such record usually is absent in the punctuation method.



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

Reply via email to