-
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
Change jdbc sources to discover more than standard schemas #1038
Conversation
Discussed offline. The desired behavior is as follows:
|
Then this PR should be ready to be merged whenever (or we can wait until we made the proper changes in the destinations first) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome! Couple questions around how this new configuration is going to be set and how it is used in discoverInternal
. Once we clear that up we can move forward.
I am fine merging once have the above figured out or waiting for changes to the destinations. We already have sources that emit streams with .
in them so it is probably fine to do this before we change destinations as they already somewhat handle this case. we're not really making anything worse.
...c/main/resources/config/STANDARD_SOURCE_DEFINITION/435bb9a5-7887-4809-aa58-28c27df0d7ad.json
Show resolved
Hide resolved
...ectors/source-jdbc/src/main/java/io/airbyte/integrations/source/jdbc/AbstractJdbcSource.java
Outdated
Show resolved
Hide resolved
...ectors/source-jdbc/src/main/java/io/airbyte/integrations/source/jdbc/AbstractJdbcSource.java
Outdated
Show resolved
Hide resolved
...ectors/source-jdbc/src/main/java/io/airbyte/integrations/source/jdbc/AbstractJdbcSource.java
Show resolved
Hide resolved
...ectors/source-jdbc/src/main/java/io/airbyte/integrations/source/jdbc/AbstractJdbcSource.java
Outdated
Show resolved
Hide resolved
be36796
to
c8b3baf
Compare
@@ -2,6 +2,6 @@ | |||
"destinationDefinitionId": "8be1cf83-fde1-477f-a4ad-318d23c9f3c6", | |||
"name": "Local CSV", | |||
"dockerRepository": "airbyte/destination-csv", | |||
"dockerImageTag": "0.1.3", | |||
"dockerImageTag": "0.1.4", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I forgot to publish this destination along with the others in #1060 so acceptance tests that are using this are not able to complete without the proper version
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One question on implementation of getExcludedInternalSchemas
. Once that is resolved, I will approve.
...ectors/source-jdbc/src/main/java/io/airbyte/integrations/source/jdbc/AbstractJdbcSource.java
Show resolved
Hide resolved
* #1038 source freshdesk - fix schema * #1038 source freshdesk: upd changelog * #1038 source freshdesk - remove temp file * #1038 source freshdesk: fix tests * #1038 source freshdesk: update expected records again * #1038 source freshdesk: rm unstable expected record * #1038 source freshdesk: edit another expected record * #1038 source freshdesk: edit another expected record * #1038 source freshdesk: fix expected records * #1038 source freshdesk: upd expected_records * #1038 source freshdesk: resolve dependency conflict * auto-bump connector version Co-authored-by: Octavia Squidington III <octavia-squidington-iii@users.noreply.github.com>
What
In this thread from the #integration channel on slack:
https://airbytehq.slack.com/archives/C01AHCDHCKE/p1605795947045500
Sam Logan pointed out that we are not currently able to select tables from other schemas than the public one in the Postgres Source. Moreover, if possible, he would like to select multiple schemas at a time for that single postgres source.
How
In this PR, I was able to discover and list tables from multiples schemas.
Unfortunately, I am hitting a road block as the usual syntax for such JDBC is to use "schema.tablename" which is not a permitted AIrbyteStream Name (as reported in #925)
This makes sense because then the destination wouldn't be able to create such a table name (for example in BigQuery)
Alternative
my_schema_name_my_table_name
(usable name for destination) but add additional special fields in the stream to specify which parts are actually for the original schema and which are for table names? (iemy_schema_name
&my_table_name
) such that the source is still able to decode the stream name into proper 'my_schema_name.my_table_name'