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

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

GitHub user gallenvara opened a pull request:

    https://github.com/apache/flink/pull/2078

    [FLINK-2985] Allow different field names for unionAll() in Table API

    Thanks for contributing to Apache Flink. Before you open your pull request, 
please take the following check list into consideration.
    If your changes take all of the items into account, feel free to open your 
pull request. For more information and/or questions please refer to the [How To 
Contribute guide](http://flink.apache.org/how-to-contribute.html).
    In addition to going through the list, please provide a meaningful 
description of your changes.
    
    - [X] General
      - The pull request references the related JIRA issue ("[FLINK-XXX] Jira 
title text")
      - The pull request addresses only one issue
      - Each commit in the PR has a meaningful commit message (including the 
JIRA id)
    
    - [X] Tests & Build
      - Functionality added by the pull request is covered by tests
      - `mvn clean verify` has been executed successfully locally or a Travis 
build has passed
    
    It is not necessary that the corresponding columns in each SELECT statement 
have the same name, but they do need to be the same data types. This PR 
supports allowing different field names for union/unionAll in Table API.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gallenvara/flink flink-2985

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/2078.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2078
    
----
commit e84d836efbb290fb79d14e3d3c6c9e13db567b72
Author: gallenvara <gallenv...@126.com>
Date:   2016-06-06T08:30:41Z

    Allow different field names for union in Table API.

----


> Allow different field names for unionAll() in Table API
> -------------------------------------------------------
>
>                 Key: FLINK-2985
>                 URL: https://issues.apache.org/jira/browse/FLINK-2985
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table API
>            Reporter: Timo Walther
>            Priority: Minor
>
> The recently merged `unionAll` operator checks if the field names of the left 
> and right side are equal. Actually, this is not necessary. The union operator 
> in SQL checks only the types and uses the names of left side.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to