You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Ismaël Mejía (Jira)" <ji...@apache.org> on 2019/12/31 09:16:00 UTC

[jira] [Updated] (BEAM-9016) Select transform (Schema-based) result order is not predictable

     [ https://issues.apache.org/jira/browse/BEAM-9016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ismaël Mejía updated BEAM-9016:
-------------------------------
    Summary: Select transform (Schema-based) result order is not predictable  (was: Select PTransform result order is not predictable)

> 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: Major
>
> 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)