relationalize is coercing timestamp columns of nested child tables to string.
Note I've tested this using Glue 4.0 locally with the AWS provided amazon/aws-glue-libs:glue_libs_4.0.0_image_01 Docker image, however it is derived from a live Glue issue we have. Our real example is much more complicated with more levels of nesting, and as such re-casting to timestamp is a possible workaround but really not ideal.
As called out in the comments with the printed output, child.val.child_timestamp has been coerced to a string. Its value is just the string representation of the Timestamp.
Question
As a user it looks like a bug as the relationalize documentation makes no mention of modifying datatypes. Is there a way to control this behavior or prevent it?
Issue
relationalize
is coercing timestamp columns of nested child tables to string.Note I've tested this using Glue 4.0 locally with the AWS provided
amazon/aws-glue-libs:glue_libs_4.0.0_image_01
Docker image, however it is derived from a live Glue issue we have. Our real example is much more complicated with more levels of nesting, and as such re-casting to timestamp is a possible workaround but really not ideal.Minimal Reproduction Script
As called out in the comments with the printed output,
child.val.child_timestamp
has been coerced to a string. Its value is just the string representation of the Timestamp.Question
As a user it looks like a bug as the
relationalize
documentation makes no mention of modifying datatypes. Is there a way to control this behavior or prevent it?