-
Notifications
You must be signed in to change notification settings - Fork 27
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
Setting filter_schemas not working as intended during catalog discovery #226
Comments
@ShahBinoy Can you double check you have the latest version installed ie |
@visch We had verified the installation with github SHA which matched with latest, I will verify after running clean command too Meanwhile attaching full log
|
@ShahBinoy Thanks for putting this in, the error is clear. It's something to do with https://github.com/meltano/sdk/blob/main/singer_sdk/connectors/sql.py#L499 not filtering / querying the way we were expecting if you still double check that will be helpful as this looks fairly confusing At a minimum we should add a test that creates a user with limited privilege's and runs the tap limited to one schema |
@ShahBinoy just wanted to verify you ran clean and were on the latest version! |
Hi @visch I think asking for Closing the issue |
I am connecting to a 3rd Party database where i only have connectivity permissions for 1 schema on Postgres DB. But after using version
0.0.3
the issue still persists.My original issue started when I experienced the error #215. But with the fix in
0.0.3
the issue still persists and I get error deep in catalog discovery phase.This is my
meltano.yml
section for extractorpdr
. We have permissions to only this schemaThis is the error I get when trying to connect to remote server where I only have permissions to check on one schema
pdr
. It is still trying to look for something inpdr_ops
schema during catalog discovery.The text was updated successfully, but these errors were encountered: