Hi community,

I have been experimenting with Select.Flattened transform and noticed that the 
field order in the flattened schema is not consistent with the order of the top 
level fields from the original schema. For example, in the original schema, we 
have field “foo” as the first field and it has a nested field “bar”. After 
applying the flattening transform, the new field “foo.bar” becomes the last 
field in the flattened schema. Seems like the order of the new fields are not 
that deterministic in the flattened schema. Is this an expected behavior? Don’t 
we guarantee any ordering of the flattened fields (e.g. being consistent with 
the original order)? Thanks!

Reply via email to