-
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 Postgres: Fix not being able to configure wal2json plugin #19985
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Affected Connector ReportNOTE
|
Connector | Version | Changelog | Publish |
---|---|---|---|
source-alloydb |
1.0.17 |
✅ | ✅ |
source-alloydb-strict-encrypt |
1.0.17 |
✅ | ⚠ (not in seed) |
source-postgres-strict-encrypt |
1.0.30 |
✅ | ⚠ (not in seed) |
- 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. |
This comment was marked as outdated.
This comment was marked as outdated.
Hi, is this why I get these errors on my Postgresql syncs ? If yes, how can I fix ?
Here the source configuration in Airbyte database :
Best regards, Pierre. |
This comment was marked as outdated.
This comment was marked as outdated.
@smartpierre yeah, that sounds related. As a workaround, I think you can downgrade source-postgres to 1.0.23. But also I'm hoping to get this PR merged in the next couple days, if you're ok with waiting til then. |
This reverts commit 0311a5a.
/test connector=connectors/source-jdbc
Build PassedTest summary info:
|
This comment was marked as outdated.
This comment was marked as outdated.
/test connector=connectors/source-mysql-strict-encrypt
Build PassedTest summary info:
|
This comment was marked as outdated.
This comment was marked as outdated.
/test connector=connectors/source-postgres-strict-encrypt
Build PassedTest summary info:
|
/test connector=connectors/source-snowflake
Build PassedTest summary info:
|
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
/test connector=connectors/source-postgres
Build PassedTest summary info:
|
/test connector=connectors/source-mysql
|
merging b/c this only affects source-postgres production code. source-mysql has broken tests but they're slightly less broken after this PR. @rodireich will publish this as part of another PR. |
@smartpierre - |
Hello @edgao we updated airbyte and our connectors, however, now it doesn't block the execution, but I can still see the errors.
Airbyte version : 0.40.26 Hope that helps, thanks for the fix 😄 |
Is this causing sync failures? (and can you post the full logs?) I think this is expected (just a misleading log message) |
No, the syncs are running properly ! But I was wondering why the log messages are still here. Marking validation errors as INFO are kinda misleading I guess. |
yeah... maybe makes sense to shift this to debug level airbyte/airbyte-json-validation/src/main/java/io/airbyte/validation/json/JsonSchemaValidator.java Lines 126 to 134 in 1a6a1c6
it's generally safe to ignore though - there are a number of cases where schema validation is actually expected to fail (e.g. after a connector spec change) |
https://github.com/airbytehq/airbyte/pull/18779/files#diff-144a4a0053518cdd47b47a03ce984697ca4081a3d49e8d70505915ab7650dadaL266-R250 accidentally switched the
plugin
config option toconst: pgoutput
. Switch it back todefault
, assuming it still passes SATs.