1 Answer
- Newest
- Most votes
- Most comments
0
Hello Logan, Based on your query I have created a glue job with RDS Postgres DB as source and Redshift as a target. Created a table with id firstname and lastname in Postgres and crawled the table. Ran the job with auto generated script from glue which is showing order lastname, id and firstname. The job is failing as you mentioned. After reordering all the occurrence id, firstname and lastname the glue job is running successful. Currently reording of columns from Glue studio feature is unavailable. For data copying if you are using Glue job then editing the glue job once will resolve the issue, even though the recrawl resulting in changing of order.
answered 10 months ago
Relevant content
- asked 9 months ago
- asked 8 months ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
I guess if you recrawl is to pick up new columns and in that case I don't see how a visual job could keep the order (I was thinking of a SelectFields transforms) while including new fields it doesn't know about (not present when the job was defined).
I suppose thats true, although the new column could just get appended to the end. What's annoying is that the order of ALL the tables is reset, not just the table with the new column.