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

Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2021/03/12 17:44:00 UTC

[jira] [Issue Comment Deleted] (BEAM-11929) DataframeTransfom, BatchRowsAsDataFrame do not preserve field order when schema created with beam.Row

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

Kenneth Knowles updated BEAM-11929:
-----------------------------------
    Comment: was deleted

(was: Because this isn't a critical bug/regression, I have removed the Fix Version. This feature can get picked up by whichever release once it is completed. Let me know if you have any questions about this.)

> DataframeTransfom, BatchRowsAsDataFrame do not preserve field order when schema created with beam.Row
> -----------------------------------------------------------------------------------------------------
>
>                 Key: BEAM-11929
>                 URL: https://issues.apache.org/jira/browse/BEAM-11929
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-py-core
>    Affects Versions: 2.26.0, 2.27.0, 2.28.0
>            Reporter: Brian Hulette
>            Assignee: Brian Hulette
>            Priority: P2
>              Labels: dataframe-api
>          Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> The workaround is to use a NamedTuple instance with DataframeTransform.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)