@kapa.ai, how can I check what is the JDBC version used by airbyte?

Thinking completed The knowledge sources don't provide a single definitive guide for checking the JDBC driver version in Airbyte, but here are a few approaches based on what's available: Checking JDBC Driver Versions in Airbyte 1. Check the Connector's Changelog / Documentation Each connector's changelog lists the JDBC driver version used. For example: • Snowflake source: The changelog shows JDBC driver upgrades over time (e.g.,

0.2.1

upgraded the Snowflake JDBC version). [Snowflake changelog] • MySQL destination: Recently upgraded from

mysql:mysql-connector-java:8.0.22

to

com.mysql:mysql-connector-j:9.6.0

. [MySQL destination changelog] 2. Check the Connector's build.gradle / build.gradle.kts The JDBC driver dependency is declared in the connector's build file. For example, the MySQL destination upgrade PR shows:

mysql:mysql-connector-java:8.0.22 -> com.mysql:mysql-connector-j:9.6.0

[MySQL JDBC upgrade PR] 3. Check the CDK's DatabaseDriver.kt The Airbyte CDK defines the JDBC driver class names used per database in DatabaseDriver.kt. This tells you which driver class is used per connector, though not the version itself. [DatabaseDriver.kt] 4. Check the CDK Logs During a Connection Check For JDBC-based connectors, the CDK can extract and log the DB/driver version during the

check

operation. As noted in the Bulk CDK changelog: [CDK changelog] > Version 0.1.15: Extract CDK logs DB version during Check for all JDBC databases. So running a connection check on your connector in the Airbyte UI and inspecting the logs should surface the JDBC driver/DB version being used. Summary: The most reliable way is to check the connector's

build.gradle

in the Airbyte GitHub repository for the specific connector you're using, or run a connection check and review the logs. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai, I'm looking at github.com/airbytehq/airbyte/blob/…/build.gradle where there's

dependencies {
    implementation 'com.amazon.redshift:redshift-jdbc42:1.2.43.1067'

this means it is using version 1.2.43.1067, right? How can I request this to upgraded?

Thinking completed Yes, you're correct! The line:

implementation 'com.amazon.redshift:redshift-jdbc42:1.2.43.1067'

means the

source-redshift

connector is using Redshift JDBC driver version 1.2.43.1067. How to Request an Upgrade You have a couple of options: 1. Open a GitHub Discussion (Recommended for feature/enhancement requests) Since this is an enhancement request, the best way is to start a GitHub Discussion under the appropriate category to request the upgrade. [Issues & Requests] 2. Open a GitHub Issue You can also submit a feature request issue on GitHub describing the need for the JDBC driver upgrade. [Issues & Requests] 3. Submit a Pull Request Yourself If you'd like to contribute the fix directly, you can: 1. Fork the

airbyte

repository 2. Update the dependency version in

build.gradle

3. Submit a PR linked to an existing issue (without a linked issue, PRs take longer to review or may be closed) 4. Include in your PR description: the problem, how your PR solves it, and your design decisions [Code Contributions] > Note: Airbyte is currently revamping its core Java destinations codebase and is not reviewing/accepting new Java connectors at this time. However, fixes and enhancements to existing connectors (like a JDBC driver upgrade) are still accepted. [Code Contributions] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai, is there already a github discussion or an issue for this?

Thinking completed I'm sorry, but the knowledge sources provided do not contain enough information to confirm whether there is already an existing GitHub issue or discussion specifically requesting an upgrade of the Redshift JDBC driver from version 1.2.43.1067 in

source-redshift

. What I can tell you is that the knowledge sources do mention the driver version limitation in the context of a bug fix: > "The DST offset issue for timestamptz is a pre-existing limitation; *a JDBC driver upgrade is the recommended follow-up*" [source-redshift fix PR] This suggests the Airbyte team is already aware that a JDBC driver upgrade is needed, but I cannot confirm whether a dedicated issue or discussion has been opened for it. I'd recommend: 1. Searching directly on GitHub Issues for terms like

source-redshift jdbc upgrade

2. Checking GitHub Discussions for similar requests 3. If nothing exists, referencing PR #79151 in your new issue, as it explicitly calls out the driver upgrade as a recommended follow-up 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai, I've opened GitHub issues for this - github.com/airbytehq/airbyte/issues/90423

Thinking completed That's great, thanks for taking the initiative to open the issue! Unfortunately, the knowledge sources I have access to don't include the content of GitHub issue #90423, so I can't comment on its current status or any responses from the Airbyte team. A few tips to help move it forward: • Reference PR #79151 in your issue if you haven't already, as it explicitly calls out the JDBC driver upgrade as a recommended follow-up [source-redshift fix PR] • Join the Airbyte community on Slack to bring visibility to the issue — the Airbyte team is active there and it can help get a faster response • Consider submitting a PR yourself if you're comfortable with it, linking back to your issue — that's often the fastest path to getting a dependency upgrade merged 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai, Is there some slack channel where I can also post my github issue to draw attention to it?

Thinking completed Yes! Based on the Airbyte Slack community guidelines, the most appropriate channel to post your issue would be: •

#ask-community-for-troubleshooting

— the recommended channel for getting help from the community and Airbyte team members [Getting Support] If you're not already a member, you can join the Airbyte Slack here. [Getting Support] A few tips when posting: [Slack Code of Conduct] • Be clear and concise — briefly explain the issue and link to your GitHub issue #90423 • Don't double-post across multiple channels • Use threads for any follow-up discussion • Don't tag specific individuals — the community will respond if they can 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.