Closed DavideBossoli88 closed 4 years ago
Hi @DavideBossoli88, thanks for reaching out.
Could you copy and paste the error Traceback (log) here, please?
Hi Igor,
below the error on the sagemaker processing job.
Traceback (most recent call last):
File "/opt/ml/processing/input/code/00_create_base_contratti.py", line 135, in
Thank you @DavideBossoli88, we will try to replicate it.
@DavideBossoli88, I was not able to replicate your issue, did you have some news from your side?
Also, could you provide more details?
@DavideBossoli88 in the meanwhile could you test the version in our development branch?
pip install git+https://github.com/awslabs/aws-data-wrangler.git@dev
We've refactored the Athena module (PR #325) and maybe it solves your issue.
Released in 1.7.0!
Hi @DavideBossoli88
It is totally off-topic, but we are stating a "Who uses AWS Data Wrangler?" section. So feel free to add yourself if you want 😄 .
has the bug been fixed?
@cotrariello84 Yes this was released in 1.7.0
Hi @malachi-constant I still have the bug in version 2.17.0. I had to use pyathena to solve it. but I 'd like to use wrangler.
@cotrariello84 Can you open a new issue with specifics on the error you're encountering as well as steps to replicate the scenario?
Hi,
I tried to run a query (setting ctas_approach = False) in a sagemaker processing job but I got some encoding errors. Then, I tried to run the same query (with the same setting) in a sagemaker notebook instance and it worked fine. I noticed that everything worked fine in the sagemaker processing job by setting ctas_approach = True, but I have no idea why.
In general, what would be the best way to handle encodings in athena.read_sql_query? Would it be possible to pass extra pandas parameters?
Thanks!