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-2644) Make it easier to test runtime-accessible ValueProvider's
Date Thu, 24 Aug 2017 02:21:00 GMT


ASF GitHub Bot commented on BEAM-2644:

GitHub user jkff opened a pull request:

    [BEAM-2644] Introduces TestPipeline.newProvider()

    R: @bjchambers 

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

    $ git pull value-provider-testing

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 #3753
commit f6f9cc1353c9f6f6f14884fd1c7f7dcdd32b5fff
Author: Eugene Kirpichov <>
Date:   2017-08-24T02:13:46Z

    [BEAM-2644] Introduces TestPipeline.newProvider()


> Make it easier to test runtime-accessible ValueProvider's
> ---------------------------------------------------------
>                 Key: BEAM-2644
>                 URL:
>             Project: Beam
>          Issue Type: New Feature
>          Components: sdk-java-core
>            Reporter: Eugene Kirpichov
>            Assignee: Davor Bonaci
> Many transforms that take ValueProvider's have different codepaths for when the provider
is accessible or not. However, as far as I can tell, there is no good way to construct a transform
with an inaccessible ValueProvider, and then test how it runs with an actual value supplied.
> The only way I could come up with is mimicking
, which is very ugly.

This message was sent by Atlassian JIRA

View raw message