[ https://issues.apache.org/jira/browse/BEAM-11391?focusedWorklogId=519617&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-519617 ]
ASF GitHub Bot logged work on BEAM-11391: ----------------------------------------- Author: ASF GitHub Bot Created on: 03/Dec/20 12:53 Start Date: 03/Dec/20 12:53 Worklog Time Spent: 10m Work Description: scwhittle commented on pull request #13472: URL: https://github.com/apache/beam/pull/13472#issuecomment-737949989 R: @aromanenko-dev I see you added this with #5019, would you be able to review? In particular, do you think using kafka create time for nexmark event timestamps should be the new default (for reading/writing) or just optional? Without these changes populating a topic by running query 0 and then reading the topic for other queries has incorrect watermark semantics, given that nexmark uses historical events by default. @reuvenlax FYI ---------------------------------------------------------------- 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 Issue Time Tracking ------------------- Worklog Id: (was: 519617) Time Spent: 20m (was: 10m) > Improve usability of Kafka source/sink for Nexmark > --------------------------------------------------- > > Key: BEAM-11391 > URL: https://issues.apache.org/jira/browse/BEAM-11391 > Project: Beam > Issue Type: Bug > Components: testing-nexmark > Reporter: Sam Whittle > Assignee: Sam Whittle > Priority: P2 > Time Spent: 20m > Remaining Estimate: 0h > > Issues: > - remove unnecessary Key deserialization which fails if keys are not set on > input > - no support for writing or reading events based upon create time, meaning > watermarks are incorrect with historical events used by nexmark by default > - no support for launching pipelines from machines unable to communicate with > kafka broker directly (due to need to determine # of partitions) -- This message was sent by Atlassian Jira (v8.3.4#803005)