[
https://issues.apache.org/jira/browse/FLINK-10290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16614797#comment-16614797
]
ASF GitHub Bot commented on FLINK-10290:
----------------------------------------
fhueske commented on issue #6666: [FLINK-10290] [table] Fix conversion error in
StreamScan and BatchScan
URL: https://github.com/apache/flink/pull/6666#issuecomment-421349773
I would not change the `equals` implementation because it might break
backwards compatibility. Maybe checking on the `TypeInformation` is not the
right choice here and we should compare `TableSchema` instead.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Conversion error in StreamScan and BatchScan
> --------------------------------------------
>
> Key: FLINK-10290
> URL: https://issues.apache.org/jira/browse/FLINK-10290
> Project: Flink
> Issue Type: Bug
> Components: Table API & SQL
> Affects Versions: 1.5.3, 1.6.0
> Reporter: wangsan
> Assignee: wangsan
> Priority: Major
> Labels: pull-request-available
>
> `RowTypeInfo#equals()` only compares field types, and fields names are not
> considered. When checking the equality of `inputType` and `internalType`, we
> should compare both filed types and field names.
> Behavior of this bug:
> A table T with schema (a: Long, b:Long, c:Long)
> SELECT b,c,a from T
> expected: b,c,a
> actually: a,b,c
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
