Github user sunjincheng121 commented on the issue:

    https://github.com/apache/flink/pull/3560
  
    HI, @KurtYoung Thanks for your attention to this PR. Good question, the 
purpose of this change is just like this JIRA's description:
    I want `ProjectionTranslator # identifyFieldReferences`  to guaranteed the 
order of the extracted field references same as input order. using `Set` just 
want to eliminate duplicate field references, and `List` also can do this, it 
is no harm to keep the `ProjectionTranslator # identifyFieldReferences` 
method's output order consistent with input.
    If the disorder results of  `ProjectionTranslator # 
identifyFieldReferences` can work, then the orderly results must also work very 
well, because the order is also a  situation of disorder. 
    What to you think?
    
    Thanks,
    SunJincheng
    



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to