[
https://issues.apache.org/jira/browse/BEAM-5299?focusedWorklogId=165676&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-165676
]
ASF GitHub Bot logged work on BEAM-5299:
----------------------------------------
Author: ASF GitHub Bot
Created on: 13/Nov/18 22:46
Start Date: 13/Nov/18 22:46
Worklog Time Spent: 10m
Work Description: aaltay commented on issue #7012: Revert "Revert "Revert
"[BEAM-5299] Define max timestamp for global w…
URL: https://github.com/apache/beam/pull/7012#issuecomment-438467609
@mxm I completely agree with you. A JIRA with explanation of what is
breaking, how to test it and what can be changed would have made this easier. I
also agree that, as long as it is possible for each such breaking case there
needs to be a new test that can catch such issues earlier.
----------------------------------------------------------------
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: 165676)
Time Spent: 15.5h (was: 15h 20m)
> Define max global window as a shared value in protos like URN enums.
> --------------------------------------------------------------------
>
> Key: BEAM-5299
> URL: https://issues.apache.org/jira/browse/BEAM-5299
> Project: Beam
> Issue Type: Improvement
> Components: beam-model, sdk-go, sdk-java-core, sdk-py-core
> Reporter: Luke Cwik
> Assignee: Maximilian Michels
> Priority: Minor
> Labels: portability
> Fix For: 2.9.0
>
> Time Spent: 15.5h
> Remaining Estimate: 0h
>
> Instead of having each language define a max timestamp themselves, define the
> max timestamps within proto to be shared across different languages.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
