beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-1718) Returning Duration.millis(Long.MAX_VALUE) in DoFn.getAllowedTimestampSkew() causes Overflow/Underflow
Date Fri, 17 Mar 2017 16:23:42 GMT


ASF GitHub Bot commented on BEAM-1718:

GitHub user tgroh opened a pull request:

    [BEAM-1718] Handle Infinite Skew in SimpleDoFnRunner

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [ ] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [ ] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [ ] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](
    Deprecate `getAllowedTimestampSkew`

You can merge this pull request into a Git repository by running:

    $ git pull infinite_skew

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2264


> Returning Duration.millis(Long.MAX_VALUE) in DoFn.getAllowedTimestampSkew() causes Overflow/Underflow
> -----------------------------------------------------------------------------------------------------
>                 Key: BEAM-1718
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-core
>    Affects Versions: 0.5.0
>            Reporter: Tobias Feldhaus
>            Assignee: Thomas Groh
> Overriding getAllowedTimestampSkew() in DoFn and returning Duration.millis(Long.MAX_VALUE)
(as suggested in the JavaDoc for allowing infinite skew) causes an Overflow/Underflow

This message was sent by Atlassian JIRA

View raw message