-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[pulsar-io] upgrade debezium version #9036
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
Conversation
|
Don't we have to update license files as well? |
|
we don't have version defined into license file |
eolivelli
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
/pulsarbot run-failure-checks |
1 similar comment
|
/pulsarbot run-failure-checks |
|
/pulsarbot run-failure-checks |
|
/pulsarbot run-failure-checks |
1 similar comment
|
/pulsarbot run-failure-checks |
|
/pulsarbot run-failure-checks |
|
@rdhabalia I think the debezium integration failed. Please take a look at those errors. |
fix compilation
|
@rdhabalia it seems that debezium integration tests are still failing. |
|
Is there anyway we can help to land this? i check the failure and see a few unrelated issue like rabbitmq and presto. |
|
/pulsarbot run-failure-tests |
|
@lxcid we have some issues on CI, if the failures are not related to the patch then we simply rerun the tests. There is an ongoing effort to fix all flakes and also to reduce overall CI time for PR validation |
|
Thanks @eolivelli for the reply! our assessment is still very rough and not reliable but we wanted to integrate pulsar for a while, and have been tracking the debezium part which is our blocker. finger cross in seeing it get landed! thanks so much! |
|
/pulsarbot run-failure-tests |
|
@rdhabalia Can you take a look at the integration failures? It might be still related to debezium. |
|
I hope I can help a bit, I'm diving the codes, and compiling. the process take a long time, meanwhile, I'm looking at the failing test and The stack trace is MySQL one. that explains why. Lines 168 to 171 in 16a2240
I'll continue to dig to see if I can figure it out. |
|
@rdhabalia this PR is superseded by the more recent #11204 |

Motivation
Upgeade debezium version for io connector.