[ 
https://issues.apache.org/jira/browse/BEAM-4415?focusedWorklogId=109530&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-109530
 ]

ASF GitHub Bot logged work on BEAM-4415:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 06/Jun/18 20:21
            Start Date: 06/Jun/18 20:21
    Worklog Time Spent: 10m 
      Work Description: szewi commented on issue #5520: [BEAM-4415] Add jenkins 
job for HDFS ParquetIOIT
URL: https://github.com/apache/beam/pull/5520#issuecomment-395200855
 
 
   Looks good to me. Jenkins job was created and during job execution proper 
testing infra was created and used by Perfkit and deleted afterwards. 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 109530)
    Time Spent: 1h 50m  (was: 1h 40m)

> Enable HDFS based Performance Test for ParquetIO
> ------------------------------------------------
>
>                 Key: BEAM-4415
>                 URL: https://issues.apache.org/jira/browse/BEAM-4415
>             Project: Beam
>          Issue Type: New Feature
>          Components: io-java-parquet, testing
>            Reporter: Łukasz Gajowy
>            Assignee: Łukasz Gajowy
>            Priority: Major
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> There already is a running job for ParquetIO on Jenkins: 
> [https://builds.apache.org/view/A-D/view/Beam/job/beam_PerformanceTests_ParquetIOIT/]
>  
> There are also Jenkins' Jobs running such tests on an HDFS cluster: 
> [https://builds.apache.org/view/A-D/view/Beam/job/beam_PerformanceTests_AvroIOIT_HDFS/]
>  
> Therefore, we should provide a Performance Test for ParquetIO running on HDFS 
> cluster.



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

Reply via email to