You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/02/15 14:05:42 UTC

[jira] [Commented] (FLINK-3850) Add forward field annotations to DataSet operators generated by the Table API

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

ASF GitHub Bot commented on FLINK-3850:
---------------------------------------

Github user tonycox commented on the issue:

    https://github.com/apache/flink/pull/3040
  
    Hi, 
    Do we need field forwarding in `DataSetMinus`, `DataSetIntersect` and `DataSetSort`?


> Add forward field annotations to DataSet operators generated by the Table API
> -----------------------------------------------------------------------------
>
>                 Key: FLINK-3850
>                 URL: https://issues.apache.org/jira/browse/FLINK-3850
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table API & SQL
>            Reporter: Fabian Hueske
>            Assignee: Nikolay Vasilishin
>
> The DataSet API features semantic annotations [1] to hint the optimizer which input fields an operator copies. This information is valuable for the optimizer because it can infer that certain physical properties such as partitioning or sorting are not destroyed by user functions and thus generate more efficient execution plans.
> The Table API is built on top of the DataSet API and generates DataSet programs and code for user-defined functions. Hence, it knows exactly which fields are modified and which not. We should use this information to automatically generate forward field annotations and attach them to the operators. This can help to significantly improve the performance of certain jobs.
> [1] https://ci.apache.org/projects/flink/flink-docs-release-1.0/apis/batch/index.html#semantic-annotations



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)