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

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

                Author: ASF GitHub Bot
            Created on: 08/Jun/18 10:03
            Start Date: 08/Jun/18 10:03
    Worklog Time Spent: 10m 
      Work Description: iemejia commented on a change in pull request #5578: 
[BEAM-3905] Update Flink Runner to Flink 1.5.0
URL: https://github.com/apache/beam/pull/5578#discussion_r194010692
 
 

 ##########
 File path: 
runners/flink/src/test/java/org/apache/beam/runners/flink/streaming/WindowDoFnOperatorTest.java
 ##########
 @@ -148,7 +148,9 @@ public void testRestore() throws Exception {
         emptyMap(),
         emptyList(),
         PipelineOptionsFactory.as(FlinkPipelineOptions.class),
-        VarLongCoder.of()
+        VarLongCoder.of(),
+        null /* key selector */ // TODO use proper key selector
 
 Review comment:
   Maybe create a JIRA for this one if you don't plan to address it in this PR.

----------------------------------------------------------------
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: 110059)
    Time Spent: 1h 40m  (was: 1.5h)

> Update Flink Runner to Flink 1.5.0
> ----------------------------------
>
>                 Key: BEAM-3905
>                 URL: https://issues.apache.org/jira/browse/BEAM-3905
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-flink
>            Reporter: Aljoscha Krettek
>            Assignee: Aljoscha Krettek
>            Priority: Major
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>




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

Reply via email to