[
https://issues.apache.org/jira/browse/BEAM-7240?focusedWorklogId=240305&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-240305
]
ASF GitHub Bot logged work on BEAM-7240:
----------------------------------------
Author: ASF GitHub Bot
Created on: 10/May/19 15:44
Start Date: 10/May/19 15:44
Worklog Time Spent: 10m
Work Description: aromanenko-dev commented on issue #8513: [BEAM-7240]
Kinesis IO Watermark Computation Improvements
URL: https://github.com/apache/beam/pull/8513#issuecomment-491335324
R: @krzysztof-tr
As original author of last changes in `KinesisWatermark`and related code,
could you take a look on this PR too, please?
----------------------------------------------------------------
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: 240305)
Time Spent: 0.5h (was: 20m)
> Kinesis IO Watermark Computation Improvements
> ---------------------------------------------
>
> Key: BEAM-7240
> URL: https://issues.apache.org/jira/browse/BEAM-7240
> Project: Beam
> Issue Type: Improvement
> Components: io-java-kinesis
> Reporter: Ajo Thomas
> Assignee: Ajo Thomas
> Priority: Minor
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently, watermarks in kinesis IO are computed taking into account the
> record arrival time in a {{KinesisRecord}}. The arrival time might not always
> be the right representation of the event time. The user of the IO should be
> able to specify how they want to extract the event time from the
> KinesisRecord.
> As the per current logic, the end user of the IO cannot control watermark
> computation in any way. A user should be able to control watermark
> computation through some custom heuristics or configurable params like time
> duration to advance the watermark if no data was received (could be due to a
> shard getting stalled. The watermark should advance and not be stalled in
> that case).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
