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

ASF GitHub Bot commented on KAFKA-8065:
---------------------------------------

mjsax commented on pull request #6393: KAFKA-8065: restore original input 
record timestamp in forward()
URL: https://github.com/apache/kafka/pull/6393
 
 
   *More detailed description of your change,
   if necessary. The PR title and PR message become
   the squashed commit message, so use a separate
   comment to ping reviewers.*
   
   *Summary of testing strategy (including rationale)
   for the feature or bug fix. Unit and/or integration
   tests are expected for any behaviour change and
   system tests should be considered for larger changes.*
   
   ### Committer Checklist (excluded from commit message)
   - [ ] Verify design and implementation 
   - [ ] Verify test coverage and CI build status
   - [ ] Verify documentation (including upgrade notes)
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Forwarding modified timestamps does not reset timestamp correctly
> -----------------------------------------------------------------
>
>                 Key: KAFKA-8065
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8065
>             Project: Kafka
>          Issue Type: Bug
>          Components: streams
>    Affects Versions: 2.0.1, 2.2.0, 2.1.1
>            Reporter: Matthias J. Sax
>            Assignee: Matthias J. Sax
>            Priority: Major
>
> Using Processor API, users can set a new output record timestamp via 
> `context.forward(..., To.all().withTimestamp(...))`. However, after the 
> forward()-call returns, the timestamp is not reset to the original input 
> record timestamp and thus a consecutive call to `context.forward(...)` 
> without `To` will use the newly set output record timestamp from before, too.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to