-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Oracle connector read all tables on ALL schemas under the same DB, not the only schema's table the user id can access #4944
Comments
hello, |
there are many schema on our Oracle DB, if no way to filter out then hit the issue #3943 |
yes, i agree @Brianlifung |
Hi, thanks for reporting this. We have a backlog of connectors today so I don't think we'll get to this until 1/2 months from now. We do accept contributions :) |
@Brianlifung @AlexandruManolache1 you want to give this another shot? |
hi @davinchia , i am now on 0.29.13-alpha, i guess i need to update to 0.29.14-alpha? |
@AlexandruManolache1 updating the connector should be sufficient |
hi, works OK, only thing worth mentioning is that the the exclusion of the default schemas remained valid- e.g.: HR |
@AlexandruManolache1 is correct yes? We don't want the default schemas to show? |
Considering the fact that we can specify just the ones we need, i would remove that filter. also, for my use case, i have some data i need to sync from HR schema. |
Got it. You do have a use case for the default schemas, so you would want to be able to specify them in the configuration and retrieve information. Is that right? |
I can pick tables from the schedule now, but failed on run |
Yes @davinchia . Exactly how you configured it now, just without excluding some in the backend. |
My I know do it supports Oracle 'CLOB' column type? I think I have an issue related to this |
@Brianlifung can you post your error in the troubleshooting channel in our Slack? |
@AlexandruManolache1 I'm going to remove the default schemas right now |
@davinchia why to remove the default schemas? having this i can work fine with the connector as there are many schemas on my Oracle DB and reach the limits without it |
The latest Oracle connector has a default filter on the schemas returned that matches the user. It will not return the system schemas anymore. |
Enviroment
Current Behavior
Step: Setting source to connect Oracle and Destination to Snowflake, passed checking on source and destination but hangs on setup connection.(there is 1 4G size table on Oracle schema)
It works on loading csv file on S3 to Snowflake, but cannot work from Oracle -> Snowflake (hangs without error) at set up connection
it hangs when set up a new connection, checking with Davin (thanks), there is log with "Caused by: io.grpc.StatusRuntimeException: RESOURCE_EXHAUSTED: grpc: received message larger than max (5420089 vs. 4194304)"
it seem loading too many tables on a db.
however I follow the steps under https://docs.airbyte.io/integrations/sources/oracle#2-create-a-dedicated-read-only-user-with-access-to-the-relevant-tables-recommended-but-optional
created a new user with a table access only, however further checking the log e.g.
2021-07-23 09:15:37 [33mWARN[m i.a.i.s.j.AbstractJdbcSource(lambda$discoverInternal$26):490 - {} - Could not convert column: "START_DATE" from table: "APEX_180200"."APEX_APPLICATION_PAGE_IR_SUB" with type: "-102". Casting to VARCHAR.
It shows up other schema "APEX_180200" (which user cannot be access), so that it may the issue Airbyte scanning all schemas, all tables under a DB while setting new connection, not the tables can be access by the oracle use id.
there are many schema, many tables at the Oracle DB, but I create a new user and 1 table on the same db for extracting tbale using airbyte.
Expected Behavior
Airbyte should scan or discover the schema the user id can be access/select ( so will not have the issue of "#3943 Discover schema fails when databases have too many tables.", the user id should can access 1 table 1 schema only
Logs
Logs
Steps to Reproduce
Are you willing to submit a PR?
Remove this with your answer.
The text was updated successfully, but these errors were encountered: