Skip to content
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

Source Oracle: schema list is not restricted to the ones specified in the source schema #8085

Closed
AlexandruManolache1 opened this issue Nov 18, 2021 · 3 comments

Comments

@AlexandruManolache1
Copy link

AlexandruManolache1 commented Nov 18, 2021

-->

Enviroment

  • Airbyte version: 0.32.0 - alpha & 0.32.1 - alpha
  • OS Version / Instance:Google Compute Engine
  • Deployment: Docker
  • Source Connector and version: Oracle DB 0.3.8
  • Destination Connector and version: google storage / 0.1.3
  • Severity: High
  • Step where error happened:Setup new connection / Upgrade Airbyte

Current Behavior

After upgrading to 0.32.0 -> i tried to create a connection from an Oracle source:
>>> seems that when creating the connections --->> the schema list is not restricted to the ones specified in the source schema setting.
So the app tried to display all users and all schemas that the user has access to.
This is causing timeout when we have schemes with hundred of tables.
I compared the logs to another app instance on 0.30.22-alpha and the connector takes only the schemas specified in the source setting. (edited)

Expected Behavior

The connections should display / use only the tables and schemas specified the source settings as it does on 0.30.22-alpha
version
image

Logs

LOG

replace this with
your long log
output here

Steps to Reproduce

  1. Create a oracle source that has access to multiple schemas
  2. Specifiy 1 schema in the source setting
  3. Create a connection using the source created at 1.
  4. Check the app logs to see what schemas are rendered.
@AlexandruManolache1 AlexandruManolache1 added the type/bug Something isn't working label Nov 18, 2021
@AlexandruManolache1
Copy link
Author

This was implemented some time ago

65efaa5 :Oracle specify schema(s) to discover. (#5779)

#5831

@AlexandruManolache1
Copy link
Author

same behavior for 0.32.1

@alafanechere alafanechere changed the title Oracle Connector Issue / 0.32.0 Source Oracle: schema list is not restricted to the ones specified in the source schema Nov 19, 2021
@alafanechere alafanechere added the area/connectors Connector related issues label Nov 19, 2021
@AlexandruManolache1
Copy link
Author

sorry, seems like our DBA added 10K+ table to the users access on a specific schema, this crashed the connection.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants