-
Notifications
You must be signed in to change notification settings - Fork 5
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
Weird query behavior: Successful query with HTTP 403 AccessDenied error #96
Comments
Hi @mraess yes I know what is happening :) It is nothing to be worries about.
If you don't like the warning message all the time. Try query caching :D This won't "tidy" the
Sorry for any confusion it has caused. Side note
Just a quick heads up, the chunk method isn't the fastest if you want to get the entire data frame. I recommend the standard |
Please let me know if this resolves you issue. P.s. thanks of such detailed ticket :D it was a great help understanding what was going on :D |
Just thinking out loud, this behaviour should really be documented |
Hey @DyfanJones , Thanks for the swift response as always! I'll definitely give this a shot today to see if that resolves the issue and then I'll follow up with you. |
@DyfanJones that did the trick! It's working now locally and on the server. We can close this out. Thanks for putting it into the documentation! |
@mraess That is perfect. I will leave this open for the time being so I can get some time to add the documentation |
…have permission to delete aws s3 objects #96
dbClearResult behaviour documentation #96
closing ticket as PR #97 has been merged |
Thanks for this package @DyfanJones. I ran into this error and turned caching on as per documentation. But now I run into a different error when querying Athena. Any thoughts? I can open a different issue if it is helpful.
|
hi @ramnathv are you able to provide the code that produced the error so i can try to replicate it :D |
hi @ramnathv I have managed to replicate the error you are coming across I will raise another issue so I can keep track of it, thanks for point this issue out 😄 . |
Issue Description
I don't know if you remember, but not to long ago we discovered an issue in paws.common together and in an issue that had to do with pulling in profiles into the
profile
parameter intodbConnect()
. Everything works fine even with AWS_PROFILE as env variables. I've been working with the updated packages and a new error prevents me from running a script on the server.When I run a query, the data is pulled and written into an
r
object (seetest_results
below). However, I also get this error message:Which is weird since the data are actually pulled and the connection to the database is successfully established. Any idea why this message is popping up?
As always, any insights would be great!
Reproducible Example
Example:
Session Info
The text was updated successfully, but these errors were encountered: