-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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: Switch back to jooq execution; add e2e special characters test #34562
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
Before Merging a Connector Pull RequestWow! What a great pull request you have here! 🎉 To merge this PR, ensure the following has been done/considered for each connector added or updated:
If the checklist is complete, but the CI check is failing,
|
1430936
to
c23c973
Compare
...main/java/io/airbyte/integrations/destination/redshift/operations/RedshiftSqlOperations.java
Outdated
Show resolved
Hide resolved
// but need to not escape bound strings. | ||
// Instead, we force jooq to always inline params, | ||
// and always call escapeStringLiteral() on the string values. | ||
new Settings().withStatementType(StatementType.STATIC_STATEMENT)); |
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 was confused reading their docs. This will switch from prepared statement to inlined statement.
There is another setting .withParamType(ParamType.INLINED)
which i think probably is what we are intending to do ? maybe the test will verify the expectation.
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.
nvm. just saw your resolved comment.
/publish-java-cdk
|
# Conflicts: # airbyte-cdk/java/airbyte-cdk/README.md # airbyte-cdk/java/airbyte-cdk/core/src/main/resources/version.properties # airbyte-integrations/connectors/destination-redshift/metadata.yaml # docs/integrations/destinations/redshift.md
/publish-java-cdk
|
8aefa29
to
e2e6523
Compare
…characters test (#34562)
…characters test (#34562)
followup to #34544.
Arguably these test cases belong in DATs, not T+D tests. At some point we should really reenable those :P
I'll submit two more PRs stacked on this one for updating the snowflake+bigquery expectedrecords files.