[
https://issues.apache.org/jira/browse/FLINK-3792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15356552#comment-15356552
]
Jark Wu commented on FLINK-3792:
--------------------------------
Do we need this before 1.1.0 release ? If yes, I can take up this issue.
We can modify {{RowTypeInfo}} constructor to take only one fieldTypes
parameter, and create default names like ("f0", "f1", ...). Because for Row we
only need to check types, we don't need to pass the fieldNames parameter to
RowTypeInfo.
> RowTypeInfo equality should not depend on field names
> -----------------------------------------------------
>
> Key: FLINK-3792
> URL: https://issues.apache.org/jira/browse/FLINK-3792
> Project: Flink
> Issue Type: Bug
> Components: Table API & SQL
> Affects Versions: 1.1.0
> Reporter: Vasia Kalavri
>
> Currently, two Rows with the same field types but different field names are
> not considered equal by the Table API and SQL. This behavior might create
> problems, e.g. it makes the following union query fail:
> {code}
> SELECT STREAM a, b, c FROM T1 UNION ALL
> (SELECT STREAM d, e, f FROM T2 WHERE d < 3)
> {code}
> where a, b, c and d, e, f are fields of corresponding types.
> {code}
> Cannot union streams of different types: org.apache.flink.api.table.Row(a:
> Integer, b: Long, c: String) and org.apache.flink.api.table.Row(d: Integer,
> e: Long, f: String)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
