- Newest
- Most votes
- Most comments
I have reproduce that for the join field, will report it to the team.
However, bear in mind that the schema is meant to reflect the data, not the other way around, if your schema doesn't match the preview then you need to do mapping/casting as required.
Thanks Gonzalo for your support. I beleive there are other problems with the Join (inner join) https://repost.aws/questions/QUd70zPw7JTkm_YGH9MsFyLw/glue-job-inner-join-unexpected-data-results
Any luck with this? I'm facing the same issue with empty schema tabs after joins. I've been running the same jobs for months now without an issue and without a need to run the data preview to infer the schema. Suddenly last week this changed and many of my jobs are showing empty schema tabs.
Hi Gonzalo, any unpdate on this? Thank you!
Relevant content
- asked 2 years ago
- Accepted Answerasked 10 months ago
- Accepted Answerasked 9 months ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
Any luck with this? I'm facing the same issue with empty schema tabs after joins. I've been running the same jobs for months now without an issue and without a need to run the data preview to infer the schema. Suddenly last week this changed and many of my jobs are showing empty schema tabs.