[
https://issues.apache.org/jira/browse/BEAM-5250?focusedWorklogId=140550&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-140550
]
ASF GitHub Bot logged work on BEAM-5250:
----------------------------------------
Author: ASF GitHub Bot
Created on: 03/Sep/18 12:00
Start Date: 03/Sep/18 12:00
Worklog Time Spent: 10m
Work Description: robertwb commented on issue #6315: [BEAM-5250] Fix
GlobalWindow's max timestamp in Python SDK
URL: https://github.com/apache/beam/pull/6315#issuecomment-418094357
Having the end of the GlobalWindow be max - 1 day seems rather arbitrary. If
it really needs to be less than MAX_TIMESTAMP, how about its immediate
predecessor? (Or is there ambiguity about milliseconds vs. microseconds to deal
with here? And even then, 2^63 - 1 micros is not likely representable as an
even number of milliseconds...) Or is the concern that windowing from global
windows -> fixed windows would overflow? In which case we'd still overflow for
days (not unreasonable) and maybe should choose something much larger.
I think it'd be worth doing at least a cursory exploration into what it
would take to "fix" Java. If that's too hard, at least we should make this a
proto value (in standard windows perhaps)?
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 140550)
Time Spent: 1h (was: 50m)
> Python Wordcount fails with Flink portable streaming
> ----------------------------------------------------
>
> Key: BEAM-5250
> URL: https://issues.apache.org/jira/browse/BEAM-5250
> Project: Beam
> Issue Type: Improvement
> Components: runner-flink
> Reporter: Thomas Weise
> Assignee: Maximilian Michels
> Priority: Major
> Labels: portability
> Time Spent: 1h
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)