1 回答
- 最新
- 投票最多
- 评论最多
1
Hi,
I have tested multiple similar use cases (CTAS + sortkey + distkey + union all + Spectrum tables). They executed successfully without any error message. I recommend in this case to open a support ticket for further analysis so you can share with the support team the real query.
Regards,
Hey Ziad, thanks a lot for testing out. Seems like something specific only for my certain table. I will reach out to support team.
相关内容
- AWS 官方已更新 2 年前
- AWS 官方已更新 1 年前
I'm not sure why this particular error is happening but I'm curious as to why you are using UNION ALL. Scanning that external table twice will take take twice as long and cost twice as much. Can you remove the UNION ALL and use CASE statements instead? But if you can't resolve this with enhancing the SQL, you should open a support case.
Hi,
Have you tried to execute the SELECT query with UNION ALL without the CREATE TABLE?
Regards,
Hey @Ziad, Yes, with table creation, query works fine.
Hey Jon, This is a simplified query, I remove some complexity to better focus on the issue. Thanks for your input.