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-postgres] : Move to new Kotlin CDK #36584

Merged
merged 22 commits into from
Apr 1, 2024
Merged

[Source-postgres] : Move to new Kotlin CDK #36584

merged 22 commits into from
Apr 1, 2024

Conversation

akashkulk
Copy link
Contributor

No description provided.

Copy link

vercel bot commented Mar 27, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
airbyte-docs ⬜️ Ignored (Inspect) Visit Preview Apr 1, 2024 8:38pm

@octavia-squidington-iii octavia-squidington-iii added the CDK Connector Development Kit label Mar 28, 2024
@akashkulk akashkulk marked this pull request as ready for review March 29, 2024 17:17
@akashkulk akashkulk requested review from a team as code owners March 29, 2024 17:17
@@ -318,7 +318,7 @@ public JdbcDatabase createDatabase(final JsonNode sourceConfig) throws SQLExcept
driverClassName,
jdbcConfig.get(JdbcUtils.JDBC_URL_KEY).asText(),
connectionProperties,
getConnectionTimeout(connectionProperties, driverClassName));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change concerns me a little bit. There's some special logic for timeouts WRT postgres, mysql or sqlserver. I think we should move getConnectionTimeout(Map<String, String>, String? out of the companion object instead of using the method that doesn't take a driverClassName

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I marked the function getConnectionTimeout(Map<String, String>, String? in the companion object in JdbcConnector as @JvmStatic. I'm not really sure why this class exists in the whole hierarchy. Feels like it can be guttedbut this seems to be the most innocuous change IMO

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that works. Thank you.
The class should eventually be in the hierarchy, and the DB specific behavior should be decided by each connector, rather than being coded inside the CDK, which means it'll eventually move back to being non-static

@@ -234,14 +232,6 @@ public boolean supportsSchemas() {
return true;
}

@Test
void testSpec() throws Exception {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why removed?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@octavia-squidington-iii octavia-squidington-iii added the area/documentation Improvements or additions to documentation label Apr 1, 2024
@akashkulk
Copy link
Contributor Author

akashkulk commented Apr 1, 2024

/publish-java-cdk

🕑 https://github.com/airbytehq/airbyte/actions/runs/8512296901
✅ Successfully published Java CDK version=0.28.20!

@akashkulk akashkulk enabled auto-merge (squash) April 1, 2024 19:18
@akashkulk akashkulk merged commit e3f3379 into master Apr 1, 2024
29 checks passed
@akashkulk akashkulk deleted the akash/pg-new-cdk branch April 1, 2024 20:51
@akashkulk akashkulk restored the akash/pg-new-cdk branch April 1, 2024 21:08
nurikk pushed a commit to nurikk/airbyte that referenced this pull request Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/connectors Connector related issues area/documentation Improvements or additions to documentation CDK Connector Development Kit connectors/source/postgres
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants