flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fabian Hueske (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3792) RowTypeInfo equality should not depend on field names
Date Wed, 20 Apr 2016 15:59:25 GMT

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

Fabian Hueske commented on FLINK-3792:

I think this should be checked at API level, not when the plan is optimized and the DataSet
/ DataStream program is constructed.
Field names are not relevant when the program (Table or SQL) is executed. Also, {{Row}} does
not provide access by name but only by position.

> 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
>    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 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

View raw message