Open manpreet1992 opened 3 years ago
@manpreet1992 unfortunately this type of rollback is not supported because the older ksql versions may not understand the query written out by the new version. In recent versions of ksqlDB, the server looks out for this condition (where there's a "newer" command) and puts the server into "degraded" mode, where the server is still usable and the queries up to that point in the command topic still run. If you absolutely need the same streams and tables, and you still have the old command topic contents around, you can simply rewrite the command topic, copying contents up to the entry that added "s4".
Describe the bug We are facing serialization exception while rolling back from version 6.1.0 to 5.5.2. Initially, we had installed ksqldb 5.5.2 with a stream named "stream2"(Avro stream). After that we upgraded it to 6.1.0 and created a new stream "S4"(Json stream). Both streams worked fine. Finally, we rolled back from 6.1.0 to 5.5.2 and started facing the serialization exception for the stream "S4".
To Reproduce Steps to reproduce the behavior, include:
CREATE STREAM stream2 WITH (kafka_topic='test2', value_format='AVRO');
CREATE STREAM s4 (c1 VARCHAR, c2 INTEGER) WITH (kafka_topic='c4', value_format='json');
Actual behaviour Ksqldb going to crashloopbackoff.
Additional context Please provide the details about the issue. If it is expected behaviour than is there any workaround to solve it? We tried two scenarios to overcome this problem. First, we dropped stream "s4" before rolling back to 5.5.2 but as the "_command_topic" topic had contained the "create stream s4 json" and "drop stream s4 json", we failed to do the rollback and stuck with the same serialization issue. Secondly, we deleted the "_command_topic" topic before rolling back. Though this workaround solved the issue and rollback was successful but we lost all our streams.
@apurvam