DBZ-7363 Debezium stops producing events on schema changes in cassandra4 #118
Conversation
|
Hi @schampilomatis. Thank you for your valuable contribution. |
|
Welcome as a new contributor to Debezium, @schampilomatis. Reviewers, please add missing author name(s) and alias name(s) to the COPYRIGHT.txt and Aliases.txt respectively. |
schampilomatis
force-pushed
the
DBZ-7363
branch
from
3ea9fec to
f9b6791
Compare
|
@schampilomatis Thanks for the PR. Could you please also add a test that will verify the new behaviour if possible? Thanks |
|
Hi @schampilomatis, thanks for your contribution. Please prefix the commit message(s) with the DBZ-xxx JIRA issue key. |
schampilomatis
force-pushed
the
DBZ-7363
branch
from
5d5577d to
5458d0d
Compare
|
@jpechane Sorry for the late response, I was away for a few weeks. I added the test to verify the behaviour. |
schampilomatis
force-pushed
the
DBZ-7363
branch
2 times, most recently
from
d8bcfc7 to
be9773d
Compare
|
@jpechane I updated the branch with formatting, can you retrigger the workflow? |
schampilomatis
force-pushed
the
DBZ-7363
branch
from
be9773d to
1818116
Compare
Adjust cassandra4 schema listener to use old table metadata Table ID when replacing the metadata in Cassandra 4 Schema Provider. Replace current logic of calculating the uuid from keyspace name and table name which does not match. Add SchemaChangeListenerTest to verify the behavior.
schampilomatis
force-pushed
the
DBZ-7363
branch
from
1818116 to
913f2c5
Compare
|
I pushed a commit with copyright header |
|
@schampilomatis Applied, thanks a lot! |
Adjust cassandra4 schema listener to use old table metadata Table ID when replacing the metadata in Cassandra 4 Schema Provider. Replace current logic of calculating the uuid from keyspace name and table name which does not match.