[ 
https://issues.apache.org/jira/browse/BEAM-5299?focusedWorklogId=161176&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-161176
 ]

ASF GitHub Bot logged work on BEAM-5299:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 31/Oct/18 15:18
            Start Date: 31/Oct/18 15:18
    Worklog Time Spent: 10m 
      Work Description: lgajowy edited a comment on issue #6381: [BEAM-5299] 
Define max timestamp for global window in proto
URL: https://github.com/apache/beam/pull/6381#issuecomment-434726637
 
 
   It seems that merging this broke Performance Tests. Example logs: 
https://builds.apache.org/view/A-D/view/Beam/job/beam_PerformanceTests_TextIOIT/1197/console
   
   I proposed a revert here: https://github.com/apache/beam/pull/6899 
   
   

----------------------------------------------------------------
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: 161176)
    Time Spent: 7h 20m  (was: 7h 10m)

> 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
>          Time Spent: 7h 20m
>  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)

Reply via email to