You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Eugene Kirpichov (JIRA)" <ji...@apache.org> on 2017/08/30 20:19:00 UTC

[jira] [Closed] (BEAM-2644) Make it easier to test runtime-accessible ValueProvider's

     [ https://issues.apache.org/jira/browse/BEAM-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eugene Kirpichov closed BEAM-2644.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 2.2.0

> Make it easier to test runtime-accessible ValueProvider's
> ---------------------------------------------------------
>
>                 Key: BEAM-2644
>                 URL: https://issues.apache.org/jira/browse/BEAM-2644
>             Project: Beam
>          Issue Type: New Feature
>          Components: sdk-java-core
>            Reporter: Eugene Kirpichov
>            Assignee: Eugene Kirpichov
>             Fix For: 2.2.0
>
>
> 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 https://github.com/apache/beam/blob/master/sdks/java/core/src/test/java/org/apache/beam/sdk/options/ValueProviderTest.java#L202 , which is very ugly.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)