fix: Introduces back the initial_waiting_seconds option for MSSQL source. - #21348
Conversation
Affected Connector ReportNOTE
|
| Connector | Version | Changelog | Publish |
|---|---|---|---|
source-mssql |
0.4.28 |
✅ | ✅ |
source-mssql-strict-encrypt |
0.4.28 |
🔵 (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-mssql
Build FailedTest summary info: |
|
/test connector=connectors/source-mssql-strict-encrypt
Build FailedTest summary info: |
…waiting-seconds' into sergio-ropero/fix/mssql-initial-waiting-seconds
|
/test connector=connectors/source-mssql-strict-encrypt
Build FailedTest summary info: |
|
/test connector=connectors/source-mssql
Build FailedTest summary info: |
|
/test connector=connectors/source-mssql-strict-encrypt
Build PassedTest summary info: |
|
/test connector=connectors/source-mssql
Build PassedTest summary info: |
|
/publish connector=connectors/source-mssql-strict-encrypt
if you have connectors that successfully published but failed definition generation, follow step 4 here |
…urce-mssql-strict-encrypt`
What
The option
initial_waiting_secondswas removed accidentally on PR #18959.See issue: #21191
How
Rolling back the
initial_waiting_secondsrelated part on above mentioned PR and adding a value to theexpected_spec.jsonfile.Recommended reading order
N/A
🚨 User Impact 🚨
Users were not able to add a delay when setting a connection between MSSQL and any destination.
UI Changes
Version 0.4.26 (master version)
Version 0.4.27 (dev version)