-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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-mssql: support Read Committed
snapshot isolation level
#28545
Conversation
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,
|
@@ -120,8 +120,8 @@ static boolean isCdc(final JsonNode config) { | |||
@VisibleForTesting | |||
static SnapshotIsolation getSnapshotIsolationConfig(final JsonNode config) { | |||
// new replication method config since version 0.4.0 | |||
if (config.hasNonNull(REPLICATION_FIELD)) { | |||
final JsonNode replicationConfig = config.get(REPLICATION_FIELD); | |||
if (config.hasNonNull(LEGACY_REPLICATION_FIELD) && config.get(LEGACY_REPLICATION_FIELD).isObject()) { |
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.
Maybe I should also add isText
case to these as well?
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.
.isTextual()
is for when replication_method was a string
.isObject()
I think is suitable for a oneOf
selection field.
Current implementation is with oneOf
so it sounds like this is correct (?)
todo: bump version (patch) and add changelog |
Read Committed
snapshot isolation level
source-mssql-strict-encrypt test report (commit
|
Step | Result |
---|
Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command
airbyte-ci connectors --name=source-mssql-strict-encrypt test
source-mssql test report (commit
|
Step | Result |
---|
Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command
airbyte-ci connectors --name=source-mssql test
@sh4sh This Looks good to me. |
source-mssql test report (commit
|
Step | Result |
---|
Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command
airbyte-ci connectors --name=source-mssql test
I said to Sunny probably we can work in a next PR to remove all confusing code between legacy and the other one. |
source-mssql-strict-encrypt test report (commit
|
Step | Result |
---|
Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command
airbyte-ci connectors --name=source-mssql-strict-encrypt test
source-mssql test report (commit
|
Step | Result |
---|
Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command
airbyte-ci connectors --name=source-mssql test
source-mssql-strict-encrypt test report (commit
|
Step | Result |
---|---|
Validate airbyte-integrations/connectors/source-mssql-strict-encrypt/metadata.yaml | ✅ |
Connector version semver check | ✅ |
QA checks | ✅ |
Build connector tar | ✅ |
Build source-mssql-strict-encrypt docker image for platform linux/x86_64 | ✅ |
./gradlew :airbyte-integrations:connectors:source-mssql-strict-encrypt:integrationTest | ❌ |
Acceptance tests | ❌ |
Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command
airbyte-ci connectors --name=source-mssql-strict-encrypt test
Until we figure out what's up with the tests, I published a pre-release here for the user to try out: https://hub.docker.com/layers/airbyte/source-mssql/1.1.1-dev.91cb51d107/images/sha256-ae1f56d0b8a3a1a059868156c63f256572a4be55cc0ad7968ae3c6aac579c889 |
The user who reported this issue tested the fix and confirmed it works 👍 |
source-mssql-strict-encrypt test report (commit
|
Step | Result |
---|---|
Validate airbyte-integrations/connectors/source-mssql-strict-encrypt/metadata.yaml | ✅ |
Connector version semver check | ✅ |
QA checks | ❌ |
Build connector tar | ✅ |
Build source-mssql-strict-encrypt docker image for platform linux/x86_64 | ✅ |
./gradlew :airbyte-integrations:connectors:source-mssql-strict-encrypt:integrationTest | ❌ |
Acceptance tests | ❌ |
Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command
airbyte-ci connectors --name=source-mssql-strict-encrypt test
/approve-and-merge reason="bug fix, tested separately as connector currently failing on master" |
source-mssql test report (commit
|
Step | Result |
---|---|
Validate airbyte-integrations/connectors/source-mssql/metadata.yaml | ✅ |
Connector version semver check | ✅ |
QA checks | ❌ |
Build connector tar | ✅ |
Build source-mssql docker image for platform linux/x86_64 | ✅ |
./gradlew :airbyte-integrations:connectors:source-mssql:integrationTest | ❌ |
Acceptance tests | ❌ |
Please note that tests are only run on PR ready for review. Please set your PR to draft mode to not flood the CI engine and upstream service on following commits.
You can run the same pipeline locally on this branch with the airbyte-ci tool with the following command
airbyte-ci connectors --name=source-mssql test
…8545) * make getSnapshotIsolationConfig grab the correct config * add object case for getDataToSyncConfig and getSnapshotIsolationConfig * update tests to use current config parameters * bump connector version * add changelog
What
Fixes #28543
How
This PR modifies two functions
getSnapshotIsolationConfig
,getDataToSyncConfig
and their applicable tests so that they are able to access the current connector config values.Recommended reading order
airbyte-integrations/connectors/source-mssql/src/main/java/io/airbyte/integrations/source/mssql/MssqlCdcHelper.java
airbyte-integrations/connectors/source-mssql/src/test/java/io/airbyte/integrations/source/mssql/MssqlCdcHelperTest.java
🚨 User Impact 🚨
This is a patch fix and should not cause breaking changes.
Pre-merge Actions
Expand the relevant checklist and delete the others.
Updating a connector
Community member or Airbyter
Airbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.