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

Posted to issues@beam.apache.org by "Michal Walenia (JIRA)" <ji...@apache.org> on 2019/03/21 08:29:00 UTC

[jira] [Closed] (BEAM-6662) Reduce code duplication in all Java IO PerformanceTests

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

Michal Walenia closed BEAM-6662.
--------------------------------
    Resolution: Fixed

> Reduce code duplication in all Java IO PerformanceTests
> -------------------------------------------------------
>
>                 Key: BEAM-6662
>                 URL: https://issues.apache.org/jira/browse/BEAM-6662
>             Project: Beam
>          Issue Type: Improvement
>          Components: testing
>            Reporter: Lukasz Gajowy
>            Assignee: Michal Walenia
>            Priority: Minor
>             Fix For: Not applicable
>
>
> After we'll make the IOIT's code to use the MetricsAPI, the test clss code will (roughly) consists of: 
>  1. testing pipeline
>  2. collecting metrics 
>  3. publishing results to console
>  4. publishing results to BigQuery
>  
> At least steps 2 - 4 are in most cases duplicated in every IOIT. We can extract a base class that will encapsulate this behaviour leaving future IOIT developers only with the need of implementing step 1.  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)