-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Destination Redshift: Fixed maximum record size for SUPER type #12940
Conversation
@adam-bloom can you sign the CLA? |
...main/java/io/airbyte/integrations/destination/redshift/operations/RedshiftSqlOperations.java
Outdated
Show resolved
Hide resolved
...main/java/io/airbyte/integrations/destination/redshift/operations/RedshiftSqlOperations.java
Outdated
Show resolved
Hide resolved
@adam-bloom Thanks for the contribution, good catch. Please, follow the Pre-merge checklist. Nothing critical from my side. |
@alexandertsukanov what parts of the checklist specifically? I attempted to run the integration tests, but they require AWS credentials for the redshift destination tests. Are these expected to be runnable in any AWS account (and I should just use my own creds) or do these need to be run by someone on the airbyte team? Otherwise, I think it's just adding a changelog entry, correct? Thanks for the few syntax suggestions - I'll clean those up along with adding the changelog entry. |
/test connector=connectors/destination-redshift
|
@adam-bloom please update the connector version in the Dockerfile please |
@marcosmarxm done |
/test connector=connectors/destination-redshift |
/test connector=connectors/destination-redshift
|
Looks like a lot of tests fails with https://github.com/airbytehq/airbyte/runs/6497341731?check_suite_focus=true Also, I see failed tests here |
Yup, the issue is with the I can take another look today, but I'm not sure how to best go about this considering:
Those two factors combined are going to make for very poor developer experience as a try to close the loop. I can't use a debugger, nor can I quickly iterate on identifying the issue. Let me see if unit tests run correctly in a local environment, and I can add a unit test to cover this case. Any other suggestions on how to best work towards a solution here? |
@alexandertsukanov @marcosmarxm would one of you be able to trigger a re-test? I think I was able to figure out the issue (and find another unrelated one while I was at it!) |
/test connector=connectors/destination-redshift
|
I have run again |
Looks good now. |
@adam-bloom could you bump the version of the connector after I will approve. Thanks. |
@alexandertsukanov where does the version still need to be bumped? The changelog and dockerfile are already updated. |
sorry, my bad, looks good so far |
/publish connector=connectors/destination-redshift
|
I'll test the auto-bumper if it's working |
Looks like something failed - it thinks 0.3.35 is already used? Is that also on another branch somewhere and this needs to go up one more? |
/publish connector=connectors/destination-redshift
|
here is the PR where the connector was published #12820 with 35 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.
thanks @adam-bloom
* fix #12680: use correct max size for SUPER type * address review comments * docs: add changelog entry * bump version * test: make large record actually too big * fix: use a method instead of member variable for correct override * fix: if overall object is invalid, don't check individual elements * feat: add unit test for isValidData * auto-bump connector version Co-authored-by: Octavia Squidington III <[email protected]>
What
See #12680: now that airbyte uses SUPER instead of VARCHAR, the max data size needs to be increased.
How
Changes the constant. #12064 changes the type for all operations (not configurable), so we don't need to be clever.
https://docs.aws.amazon.com/redshift/latest/dg/r_SUPER_type.html
Also see https://docs.aws.amazon.com/redshift/latest/dg/limitations-super.html - the VARCHAR check is retained, but only used for fields within the SUPER object instead of the object overall.
Recommended reading order
N/A
🚨 User Impact 🚨
N/A
Pre-merge Checklist
Community member or Airbyter
airbyte_secret
./gradlew :airbyte-integrations:connectors:<name>:integrationTest
.README.md
bootstrap.md
. See description and examplesdocs/integrations/<source or destination>/<name>.md
including changelog. See changelog exampleAirbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
/test connector=connectors/<name>
command is passing/publish
command described hereTests
Unit
Put your unit tests output here.
Integration
Put your integration tests output here.
Acceptance
Put your acceptance tests output here.