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

Posted to issues@flink.apache.org by "Jark Wu (Jira)" <ji...@apache.org> on 2019/11/13 05:41:00 UTC

[jira] [Resolved] (FLINK-14731) LogicalWatermarkAssigner should use specified trait set when doing copy

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

Jark Wu resolved FLINK-14731.
-----------------------------
    Fix Version/s: 1.10.0
         Assignee: Liya Fan
       Resolution: Fixed

1.10.0: 276e850aaee78d30a5a6e5eec1f8dbd0b167a9c7

> LogicalWatermarkAssigner should use specified trait set when doing copy
> -----------------------------------------------------------------------
>
>                 Key: FLINK-14731
>                 URL: https://issues.apache.org/jira/browse/FLINK-14731
>             Project: Flink
>          Issue Type: Bug
>          Components: Table SQL / Planner
>            Reporter: Liya Fan
>            Assignee: Liya Fan
>            Priority: Trivial
>              Labels: pull-request-available
>             Fix For: 1.10.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> In LogicalWatermarkAssigner#copy method, creating the new LogicalWatermarkAssigner object should use the trait set from the input parameter, instead of the trait set of the current object. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)