-
Notifications
You must be signed in to change notification settings - Fork 89
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
Support Include/Exclude Lists #56
Comments
Thanks. Parameter in config will work na ? |
I tried providing schema and table name to check if it works. I am getting error : raise OperationalError(query_execution.state_change_reason) pyathena.error.OperationalError: SYNTAX_ERROR: line 1:8: Column 'request_timestamp' cannot be resolvedI don't request_timestamp column. |
I just merged it to master. Can you downloading the code and run
|
oh - can you try |
Yea- I forgot to add it to aws. Fixing that now. |
yes. config looks good. |
Support was missed in previous commit. Again - fix tokern#56
Support was missed in previous commit. Again - fix #56
Getting below error:
|
is there a line number ? Stack trace ? |
I found a gap in my testing. I'll add a test and fix the bug. |
Athena is working for shallow type scan. For deep scan it throws below error:
HIVE_UNKNOWN_ERROR: All access to this object has been disabled (Service: Amazon S3; Status Code: 403; Error Code: AllAccessDisabled; Request ID:
Is there any parameter in config where we can pass specific DB to scan ?
Originally posted by @jayeshagwan1 in #55 (comment)
The text was updated successfully, but these errors were encountered: