[
https://issues.apache.org/jira/browse/BEAM-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17314942#comment-17314942
]
Brian Hulette commented on BEAM-9016:
-------------------------------------
It seem reasonable to guarantee the field order is consistent with the order
specified in the transform, I don't see a reason not to.
I'm curious what [~yangzhang] was doing where field order mattered though, in
general other schema transforms reference fields by name.
> Select transform (Schema-based) result order is not predictable
> ---------------------------------------------------------------
>
> Key: BEAM-9016
> URL: https://issues.apache.org/jira/browse/BEAM-9016
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-core
> Reporter: Yang Zhang
> Priority: P3
> Labels: Clarified
>
> pipeline.apply(Select.fieldNames("x", "y"))
> pipeline.apply(Select.fieldNames("a", "b"))
> The returned output order is not predictable. In the above two examples,
> field `x` may return first, while field `a` (also queries in the first place)
> may return in the second place.
>
> Shall we add `withOrderByFieldInsertionOrder` to fieldAccessDescriptor in
> Select PTransform, so that the return order is predictable?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
