-
Notifications
You must be signed in to change notification settings - Fork 14.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SqlToS3Operator not able to write data with partition_cols provided. #30382
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval. |
@utkarsharma2 Want to take this one? :) |
@amolsr Feel free to open a PR to fix it |
@amolsr Would you like to pair on this one? |
Yeah sure. |
I would like to work on this issue ,can you please assign this to me To fix this error, I want to try the following steps: 1.Check if the /tmp directory exists and is writable. |
@PasunuriSrinidhi there is an open (and active) PR linked to this issue, if you want to help closing it, you can review and test the created PR #30460. |
@hussein-awala I will review and test the created PR |
Apache Airflow Provider(s)
amazon
Versions of Apache Airflow Providers
I am using the standard operator version which comes with apache/airflow:2.5.2.
Apache Airflow version
2.5.2
Operating System
Ubuntu 22.04.2 LTS
Deployment
Official Apache Airflow Helm Chart
Deployment details
I have used a simple docker compose setup can using the same in my local.
What happened
I am using SqlToS3Operator in my Dag. I need to store the data using the partition col. The operator writes the data in a temporary file but in my case it should be a folder. I am getting the below error for the same.
What you think should happen instead
The Operator should have supported the partition col as well.
How to reproduce
I am using the below code snipet for the same.
This could be using to reproduce the same.
Anything else
I believe this logic should be updated for the same.
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: