You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/06/03 18:30:00 UTC

[jira] [Commented] (BEAM-2632) TextIOReadTest creates pipelines with non-unique application names

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

Kenneth Knowles commented on BEAM-2632:
---------------------------------------

This issue has been migrated to https://github.com/apache/beam/issues/18398

> TextIOReadTest creates pipelines with non-unique application names
> ------------------------------------------------------------------
>
>                 Key: BEAM-2632
>                 URL: https://issues.apache.org/jira/browse/BEAM-2632
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-core
>            Reporter: Kenneth Knowles
>            Priority: P4
>              Labels: Clarified, newbie, starter
>
> The test {{TextIOReadTest}} uses a loop to create a few tests within a single test method. This results in a pipeline with non-unique applied transform nodes.
> Perhaps the best way to fix this is to use a JUnit {{Paramaterized}} test suite, or multiple. It does seem that the test is basically doing the full product of empty/tiny/large with various compression types.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)