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

DBZ-6839 Fix PostgresConnectorIT#shouldAddNewFieldToSourceInfo #4807

Merged
merged 1 commit into from
Aug 25, 2023

Conversation

vjuranek
Copy link
Member

PostgresConnectorIT#shouldAddNewFieldToSourceInfo fails only when run together with other tests and the failure is random. It seem there is a caching issue in Apicuro, when test_server.s1.a-value artifact references io.debezium.connector.postgresql.Source version 1, which hasnt't newField field and this reference is used also in shouldAddNewFieldToSourceInfo where artifact with version 2 should be used. Using dedicated table and thus creating new artifact in Apucurio should fix this issue.

Also remove unused variable from CustomPostgresSourceInfoStructMaker.

https://issues.redhat.com/browse/DBZ-6839

PostgresConnectorIT#shouldAddNewFieldToSourceInfo fails only when run
together with other tests and the failure is random. It seem there is
a caching issue in Apicuro, when `test_server.s1.a-value` artifact
references `io.debezium.connector.postgresql.Source` version 1, which
hasnt't `newField` field and this reference is used also in
`shouldAddNewFieldToSourceInfo` where artifact with version 2 should
be used. Using dedicated table and thus creating new artifact in
Apucurio should fix this issue.

Also remove unused variable from `CustomPostgresSourceInfoStructMaker`.
@jpechane jpechane merged commit 28b06e6 into debezium:main Aug 25, 2023
24 of 25 checks passed
@jpechane
Copy link
Contributor

@vjuranek Applied, thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants