Ksql-cli: When message with wrong format or blank line is published, ksql stops processing the entire stream/table altogether about ksql HOT 4 CLOSED

@hemalatha-amrutha This has been the default behavior in Kafka Streams, however, in 1.0 release of Kafka we have the option of specifying the behavior as described in KIP-161 (https://cwiki.apache.org/confluence/display/KAFKA/KIP-161%3A+streams+deserialization+exception+handlers)
You should be able to set the "default.deserialization.exception.handler" config variable to the name of LogAndContinueExceptionHandler class using the SET statement.
Please let us know if you encounter any issues in using the above configuration with Kafka 1.0.

from ksql.

@hjafarpour : We should evaluate whether, moving forward, we should change the default settings of KSQL in this regard.

from ksql.

Hi @hjafarpour , I am getting similar issues with
ksql> show streams;

Stream Name | Kafka Topic | Format

PAGEVIEWS | pageviews | JSON
ksql> select * from PAGEVIEWS;
Failed to deserialize value for record. topic=pageviews, partition=0, offset=7107
Query terminated

are they related. Sorry new to the community and the guidelines to ask questions.

from ksql.

I believe the new default for KSQL is to log error and continue when deserialization fails. Closing this out.

from ksql.