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 2020/05/14 13:53:00 UTC

[jira] [Comment Edited] (FLINK-17693) Add createTypeInformation to DynamicTableSink#Context

    [ https://issues.apache.org/jira/browse/FLINK-17693?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17107314#comment-17107314 ] 

Jark Wu edited comment on FLINK-17693 at 5/14/20, 1:52 PM:
-----------------------------------------------------------

[~ykt836], returning a TypeInformation is more flexible. TypeSerailizer can be derived from TypeInformation. 


was (Author: jark):
[~ykt836], returning a TypeInformation is more flexible. TypeSerailizer can derived from TypeInformation. 

> Add createTypeInformation to DynamicTableSink#Context
> -----------------------------------------------------
>
>                 Key: FLINK-17693
>                 URL: https://issues.apache.org/jira/browse/FLINK-17693
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Table SQL / API
>            Reporter: Jark Wu
>            Assignee: Jark Wu
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.11.0
>
>
> Currently, we have {{createTypeInformation}} on {{DynamicTableSource#Context}}, but not on {{DynamicTableSink#Context}}.
> In some sink connectors, we need to buffer the {{RowData}} and flush at some interval. So we need to copy the {{RowData}} if object reuse is enabled, then the internal TypeInformation is needed to get the RowData TypeSerializer#copy. 



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