Transformations: Rename fields in case of a conflict in the destination
It would be good to be able to rename fields in the case of the conflict in the destination, so the source does not need to be modified. For example, Redshift has a reserved word "oid" that cannot exist on the source, or an error occurs.
-
Hey Phillip, thanks for reaching out regarding this! Do you mind elaborating on a specific experience where this is occurring for you?
Please sign in to leave a comment.
Comments
1 comment