Skip to content

Conversation

@findinpath
Copy link
Contributor

Description

The version 2.2.0 and 2.2.1 of the driver are introducing a
regression in coping with long table names.
The regression has been documented in the issue
aws/amazon-redshift-jdbc-driver#148

Additional context and related issues

aws/amazon-redshift-jdbc-driver#148

#27445

Release notes

(x) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text:

## Section
* Fix some things. ({issue}`issuenumber`)

@cla-bot cla-bot bot added the cla-signed label Nov 26, 2025
@github-actions github-actions bot added docs iceberg Iceberg connector redshift Redshift connector labels Nov 26, 2025
@findinpath findinpath force-pushed the findinpath/downgrade-redshift-2.1.0.30 branch from dd2703a to ae5953c Compare November 26, 2025 04:46
@ebyhr
Copy link
Member

ebyhr commented Nov 26, 2025

Could you rebase on master to resolve conflicts?

The version 2.2.0 and 2.2.1 of the driver are introducing a
regression in coping with long table names.
The regression has been documented in the issue
aws/amazon-redshift-jdbc-driver#148
@findinpath findinpath force-pushed the findinpath/downgrade-redshift-2.1.0.30 branch from ae5953c to 45d5b99 Compare November 26, 2025 05:03
@ebyhr
Copy link
Member

ebyhr commented Nov 26, 2025

/test-with-secrets sha=45d5b996e598be16ce322a9c8711cdbb04199cab

@github-actions
Copy link

The CI workflow run with tests that require additional secrets has been started: https://github.com/trinodb/trino/actions/runs/19693522439

@ebyhr ebyhr merged commit 703e897 into trinodb:master Nov 26, 2025
19 checks passed
@github-actions github-actions bot added this to the 479 milestone Nov 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed docs iceberg Iceberg connector redshift Redshift connector

Development

Successfully merging this pull request may close these issues.

3 participants