[ https://issues.apache.org/jira/browse/BEAM-3851?focusedWorklogId=81978&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-81978 ]
ASF GitHub Bot logged work on BEAM-3851: ---------------------------------------- Author: ASF GitHub Bot Created on: 19/Mar/18 19:19 Start Date: 19/Mar/18 19:19 Worklog Time Spent: 10m Work Description: XuMingmin commented on issue #4868: [BEAM-3851] Option to preserve element timestamp while publishing to Kafka. URL: https://github.com/apache/beam/pull/4868#issuecomment-374335756 I would suggest to make the change together, but I would prefer to a `TimestampFn` instead of `ctx.timestamp()`, --I find `ctx.timestamp()` of `earlyFiring`/`lateFiring`/`ontimeFiring` is quite complex and is not what I want sometime. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on 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 Issue Time Tracking ------------------- Worklog Id: (was: 81978) Time Spent: 0.5h (was: 20m) > Support element timestamps while publishing to Kafka. > ----------------------------------------------------- > > Key: BEAM-3851 > URL: https://issues.apache.org/jira/browse/BEAM-3851 > Project: Beam > Issue Type: Improvement > Components: io-java-kafka > Affects Versions: 2.3.0 > Reporter: Raghu Angadi > Assignee: Raghu Angadi > Priority: Major > Fix For: 2.4.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > KafkaIO sink should support using input element timestamp for the message > published to Kafka. Otherwise there is no way for user to influence the > timestamp of the messages in Kafka sink. -- This message was sent by Atlassian JIRA (v7.6.3#76005)