Repository navigation
fix-postgres-cdc-npe:do not put null in properties - #24271
Conversation
|
/test connector=connectors/source-postgres
Build PassedTest summary info: |
|
/test connector=connectors/source-postgres-strict-encrypt
Build PassedTest summary info: |
Affected Connector ReportNOTE
|
| Connector | Version | Changelog | Publish |
|---|---|---|---|
source-alloydb |
2.0.6 |
✅ | ✅ |
source-alloydb-strict-encrypt |
2.0.6 |
🔵 (ignored) |
🔵 (ignored) |
source-mssql |
1.0.4 |
✅ | ✅ |
source-mysql |
2.0.6 |
✅ | ✅ |
source-postgres |
2.0.6 |
✅ | ✅ |
source-postgres-strict-encrypt |
2.0.6 |
🔵 (ignored) |
🔵 (ignored) |
- 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.
✅ Other Modules (0)
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. |
|
/test connector=connectors/source-alloydb-strict-encrypt
Build PassedTest summary info: |
|
/test connector=connectors/source-alloydb
Build PassedTest summary info: |
|
/publish connector=connectors/source-alloydb
if you have connectors that successfully published but failed definition generation, follow step 4 here |
|
/publish connector=connectors/source-alloydb-strict-encrypt
if you have connectors that successfully published but failed definition generation, follow step 4 here |
|
/publish connector=connectors/source-postgres-strict-encrypt
if you have connectors that successfully published but failed definition generation, follow step 4 here |
|
/publish connector=connectors/source-postgres
if you have connectors that successfully published but failed definition generation, follow step 4 here |
* fix-postgres-cdc-npe:do not put null in properties * version bump + change log * auto-bump connector version * manual bump --------- Co-authored-by: Octavia Squidington III <octavia-squidington-iii@users.noreply.github.com>
* fix-postgres-cdc-npe:do not put null in properties * version bump + change log * auto-bump connector version * manual bump --------- Co-authored-by: Octavia Squidington III <octavia-squidington-iii@users.noreply.github.com>
issue : #22298