beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-27) Add user-ready API for interacting with timers
Date Sat, 17 Dec 2016 04:44:59 GMT

    [ https://issues.apache.org/jira/browse/BEAM-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15756313#comment-15756313
] 

ASF GitHub Bot commented on BEAM-27:
------------------------------------

GitHub user kennknowles opened a pull request:

    https://github.com/apache/incubator-beam/pull/1652

    [BEAM-27, BEAM-362] Move InMemoryTimerInternals to runners-core; restore a deprecated
copy in its place

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
    
     - [x] 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).
     - [x] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [x] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt).
    
    ---
    
    This is a replay of ec0bf7b4023ff75f4ec6723d2e77ed507eb57c51 with an additional adapter
commit that should enable integration tests to succeed.
    
    Note that this configuration of commits works will with the current capabilities of `git`
and GitHub.  This behavior is not baked into the history, but is calculated dynamically by
both, so it may improve over time.
    
    Notes on what would happen if this were done in one commit:
    
     - `git log --follow` finds the history
     - `git diff --find-copies` finds the copy
     - `git blame --find-copies-harder` finds the copy, but `--find-copies` does not
    
    I don't recall which level GitHub's UI works with, but the most important two are `git
log` and `git blame`. To make sure it works without any of the above, two commits is better.

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

    $ git pull https://github.com/kennknowles/incubator-beam InMemoryTimerInternals

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

    https://github.com/apache/incubator-beam/pull/1652.patch

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

    This closes #1652
    
----
commit 6effd6c93587d1c0a02ba9285b47d165ae5c517d
Author: Kenneth Knowles <klk@google.com>
Date:   2016-12-16T04:45:56Z

    Move InMemoryTimerInternals to runners-core

commit 557d2d724c53233ad9d34c9239ff5cf77b754d73
Author: Kenneth Knowles <klk@google.com>
Date:   2016-12-17T04:22:59Z

    Restore SDK's InMemoryTimerInternals, deprecated

----


> Add user-ready API for interacting with timers
> ----------------------------------------------
>
>                 Key: BEAM-27
>                 URL: https://issues.apache.org/jira/browse/BEAM-27
>             Project: Beam
>          Issue Type: New Feature
>          Components: sdk-java-core
>            Reporter: Kenneth Knowles
>            Assignee: Kenneth Knowles
>
> Pipeline authors will benefit from a different factorization of interaction with underlying
timers. The current APIs are targeted at runner implementers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message