...

1. completely change the semantics of the input stream from event stream to changelog stream any null-values will still be serialized, and if the resulted bytes are also null they will be interpreted as "deletes" to the materialized KTable (i.e. tombstones in the changelog stream).
2. materializing these KTables should only be allowed if the overloaded function with Materialized is used (and if optimization is turned on it may still be only logically materialized if the queryable name is not set).
3. Materialization of the KTable will follow the usual process:
   1. if Optimization is turned off, the KTable will always be materialized (but the store will not be queryable)
   2. if Optimization is turned on and if .toTable() is used, the Ktable may or may not be materialized. The store still cannot be queried.
   3. if .toTable(final Materialized<K, VR, KeyValueStore<Bytes, byte[]>> materialized) is used irrespective of the optimization strategy used the KTable will be materialized and will be queryable

Public Interfaces

Two functions will need to be added to the KStream interface:

...