Skip to content
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

Debezium failing silently on invalid SSL configuration #31579

Closed
akashkulk opened this issue Oct 18, 2023 · 1 comment · Fixed by #33658
Closed

Debezium failing silently on invalid SSL configuration #31579

akashkulk opened this issue Oct 18, 2023 · 1 comment · Fixed by #33658
Assignees
Labels
needs-triage team/db-dw-sources Backlog for Database and Data Warehouse Sources team

Comments

@akashkulk
Copy link
Contributor

Topic

No response

Relevant information

Debezium is failing silently on a bad SSL configuration in this sync : https://cloud.airbyte.com/workspaces/7c1a9ee7-09f6-49fe-bf98-8746ed05697e/connections/606a1f43-0f9c-44f2-a47b-3458b0e31cba/job-history#5056806::0

We believe that the newest version of Debezium addresses this issue, so will need to upgrade all connectors to use this version (2.4.0)

@akashkulk akashkulk added needs-triage team/db-dw-sources Backlog for Database and Data Warehouse Sources team labels Oct 18, 2023
@akashkulk
Copy link
Contributor Author

Debezium seems to be silently failing with an invalid configuration. Raised this issue with the community : https://debezium.zulipchat.com/#narrow/stream/302529-community-general/topic/Invalid.20Connector.20configuration.20not.20throwing.20an.20exception

stephane-airbyte added a commit that referenced this issue Jan 9, 2024
Looks like the logic of handling the result of the debezium engine was slightly wrong. Wee were assining the local `error` field, and then checking itf it was not null, and overriding it in that case. The truth is that the engine can fail without filling in the `error` field, but still fill in the `message` field. So the new logic uses the `message` field if `error` is null

fixes #31579
jatinyadav-cc pushed a commit to ollionorg/datapipes-airbyte that referenced this issue Feb 26, 2024
Looks like the logic of handling the result of the debezium engine was slightly wrong. Wee were assining the local `error` field, and then checking itf it was not null, and overriding it in that case. The truth is that the engine can fail without filling in the `error` field, but still fill in the `message` field. So the new logic uses the `message` field if `error` is null

fixes airbytehq#31579
jatinyadav-cc pushed a commit to ollionorg/datapipes-airbyte that referenced this issue Feb 26, 2024
Looks like the logic of handling the result of the debezium engine was slightly wrong. Wee were assining the local `error` field, and then checking itf it was not null, and overriding it in that case. The truth is that the engine can fail without filling in the `error` field, but still fill in the `message` field. So the new logic uses the `message` field if `error` is null

fixes airbytehq#31579
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage team/db-dw-sources Backlog for Database and Data Warehouse Sources team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants