-
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
mssql-source:upgrade debezium version to 1.9.6 #18732
Conversation
/test connector=connectors/source-mssql
Build PassedTest summary info:
|
NOTE
|
NOTE
|
/test connector=connectors/source-mysql
Build PassedTest summary info:
|
/test connector=connectors/source-postgres
Build PassedTest summary info:
|
/test connector=connectors/source-mssql
Build PassedTest summary info:
|
Thanks Subodh - could you quickly summarize the main changes in the PR description in this PR, and the ones needed to happen to upgrade the ms-sql connector to dbz 1.9.6? |
@@ -11,7 +11,7 @@ dependencies { | |||
|
|||
implementation 'io.debezium:debezium-api:1.9.6.Final' | |||
implementation 'io.debezium:debezium-embedded:1.9.6.Final' | |||
// implementation 'io.debezium:debezium-connector-sqlserver:1.9.2.Final' | |||
implementation 'io.debezium:debezium-connector-sqlserver:1.9.6.Final' |
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 just wanted to make sure that what was forgotten in Postgres (TINYINT(1)
?) is taken care of here.
import org.slf4j.Logger; | ||
import org.slf4j.LoggerFactory; | ||
|
||
public class FirstRecordWaitTimeUtil { |
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.
Can you add a brief class comment here?
/publish connector=connectors/source-mssql-strict-encrypt
if you have connectors that successfully published but failed definition generation, follow step 4 here |
/publish connector=connectors/source-mssql
if you have connectors that successfully published but failed definition generation, follow step 4 here |
Affected Connector ReportNOTE
|
Connector | Version | Changelog | Publish |
---|---|---|---|
source-mssql |
0.4.25 |
✅ | ✅ |
source-mssql-strict-encrypt |
0.4.25 |
✅ | ⚠ (not in seed) |
source-mysql |
1.0.11 |
✅ | ✅ |
source-mysql-strict-encrypt |
1.0.11 |
✅ | ⚠ (not in seed) |
source-postgres |
1.0.22 |
✅ | ✅ |
- See "Actionable Items" below for how to resolve warnings and errors.
✅ Destinations (0)
Connector | Version | Changelog | Publish |
---|
- See "Actionable Items" below for how to resolve warnings and errors.
Actionable Items
(click to expand)
Category | Status | Actionable Item |
---|---|---|
Version | ❌ mismatch |
The version of the connector is different from its normal variant. Please bump the version of the connector. |
⚠ doc not found |
The connector does not seem to have a documentation file. This can be normal (e.g. basic connector like source-jdbc is not published or documented). Please double-check to make sure that it is not a bug. |
|
Changelog | ⚠ doc not found |
The connector does not seem to have a documentation file. This can be normal (e.g. basic connector like source-jdbc is not published or documented). Please double-check to make sure that it is not a bug. |
❌ changelog missing |
There is no chnagelog for the current version of the connector. If you are the author of the current version, please add a changelog. | |
Publish | ⚠ not in seed |
The connector is not in the seed file (e.g. source_definitions.yaml ), so its publication status cannot be checked. This can be normal (e.g. some connectors are cloud-specific, and only listed in the cloud seed file). Please double-check to make sure that it is not a bug. |
❌ diff seed version |
The connector exists in the seed file, but the latest version is not listed there. This usually means that the latest version is not published. Please use the /publish command to publish the latest version. |
/publish connector=connectors/source-mssql-strict-encrypt
if you have connectors that successfully published but failed definition generation, follow step 4 here |
/test connector=connectors/source-mssql |
Issue : #15248
Tested this locally.