You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Kurt Young (JIRA)" <ji...@apache.org> on 2017/03/17 09:24:43 UTC
[jira] [Comment Edited] (FLINK-6097) Guaranteed the order of the
extracted field references
[ https://issues.apache.org/jira/browse/FLINK-6097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15929620#comment-15929620 ]
Kurt Young edited comment on FLINK-6097 at 3/17/17 9:24 AM:
------------------------------------------------------------
What is the purpose of keeping the field order?
And when function call involved, what is the order of the parameters? Like {{select func(a, b, c) from t}}, should the order be {{a, b, c}} or {{c, b, a}}
was (Author: ykt836):
What is the purpose of keeping the field order? And when function call involved, what is the order of the parameters? Like {{select func(a, b, c) from t}}, should the order be {{a, b, c}} or {{c, b, a}}
> Guaranteed the order of the extracted field references
> ------------------------------------------------------
>
> Key: FLINK-6097
> URL: https://issues.apache.org/jira/browse/FLINK-6097
> Project: Flink
> Issue Type: Improvement
> Components: Table API & SQL
> Reporter: sunjincheng
> Assignee: sunjincheng
>
> The current `ProjectionTranslator # identifyFieldReferences` method uses the` Set` temporary save field, causing the field to be out of order, although the out of order is also working, but I think the order is better than out of order. So I want to improve it,Orderly extraction field.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)