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

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

                Author: ASF GitHub Bot
            Created on: 15/Jun/19 11:39
            Start Date: 15/Jun/19 11:39
    Worklog Time Spent: 10m 
      Work Description: mxm commented on issue #8174: [BEAM-6683] add 
createCrossLanguageValidatesRunner task
URL: https://github.com/apache/beam/pull/8174#issuecomment-502359225
 
 
   Any update here? Would be great to get this in.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


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

    Worklog Id:     (was: 260870)
    Time Spent: 14h 40m  (was: 14.5h)

> Add an integration test suite for cross-language transforms for Flink runner
> ----------------------------------------------------------------------------
>
>                 Key: BEAM-6683
>                 URL: https://issues.apache.org/jira/browse/BEAM-6683
>             Project: Beam
>          Issue Type: Test
>          Components: testing
>            Reporter: Chamikara Jayalath
>            Assignee: Heejong Lee
>            Priority: Major
>          Time Spent: 14h 40m
>  Remaining Estimate: 0h
>
> We should add an integration test suite that covers following.
> (1) Currently available Java IO connectors that do not use UDFs work for 
> Python SDK on Flink runner.
> (2) Currently available Python IO connectors that do not use UDFs work for 
> Java SDK on Flink runner.
> (3) Currently available Java/Python pipelines work in a scalable manner for 
> cross-language pipelines (for example, try 10GB, 100GB input for 
> textio/avroio for Java and Python). 
>  



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

Reply via email to