You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jun Zhang (JIRA)" <ji...@apache.org> on 2018/11/22 03:40:00 UTC

[jira] [Comment Edited] (FLINK-9870) Support field mapping and time attributes for table sinks

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

Jun Zhang edited comment on FLINK-9870 at 11/22/18 3:39 AM:
------------------------------------------------------------

[~twalthr] I assume time attributes are not relevant to table sinks and only make sense when registering table source, why these interfaces need to be implemented by table sinks? 

In our case, some tables should be registered as both source and sink. When they are used as source, time attributes are necessary, but when used as sink time attributes are just ignored.


was (Author: junz):
[~twalthr] I assume time attributes are not relevant to table sinks and only make sense when registering table source, why these interfaces need to be implemented by table sinks? 

> Support field mapping and time attributes for table sinks
> ---------------------------------------------------------
>
>                 Key: FLINK-9870
>                 URL: https://issues.apache.org/jira/browse/FLINK-9870
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table API &amp; SQL
>    Affects Versions: 1.6.0
>            Reporter: Timo Walther
>            Assignee: Timo Walther
>            Priority: Major
>             Fix For: 1.8.0
>
>
> FLINK-7548 reworked the table source design and implemented the interfaces {{DefinedFieldMapping}}, {{DefinedProctimeAttribute}}, and {{DefinedRowtimeAttributes}}.
> However, these interfaces need to be implemented by table sinks as well in order to map a table back into a sink similar how source do it for reading input data.
> The current unified sink design assumes that this is possible.



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