[
https://issues.apache.org/jira/browse/FLINK-2985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15360898#comment-15360898
]
ASF GitHub Bot commented on FLINK-2985:
---------------------------------------
Github user gallenvara commented on the issue:
https://github.com/apache/flink/pull/2078
Hi @wuchong , thanks a lot for your advice. With default fieldnames may
cause same content of `input1` and `input2` in `CodeGenerator`. Comparing the
`inputTerm` is a easy and effective way to avoid it. :)
> 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 & SQL
> 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)
