-
Notifications
You must be signed in to change notification settings - Fork 22
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
Need to restart Cassandra node if drop + create table with different primary key fields #77
Comments
Even after the node restarts, the dirty topic schema should be updated otherwise you'll get
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Let's say you create a table
table1
in this way(key text, value text, primary key (text)) with cdc=true
. Then the agent will cache the schema for the primary keys in memory. If the user drop the table and recreate in with the same name and in the same keyspace but with different primary keys fields, you'll get an error like:After that the agent is not able to go forward and you have to restart the agent (therefore the node) to make it work again.
Note that other tables still continue to be sent to Pulsar
The text was updated successfully, but these errors were encountered: