With "default" I mean "FailOnInvalidTimestampExtractor" that is set as
config if you don't overwrite it. Thus, for through() the setting in
StreamsConfig is ignored if you set a custom extractor.
>> So, KStream.through() and KStream.to()-Topology.stream() are not
>> semantically equivalent? Is the
> it would be invalid to specify a custom extractor (for correctness
reasons, we enforce the default timestamp extractor)
"default timestamp extractor" meaning the one that was used when reading
the input record?
So, KStream.through() and KStream.to()-Topology.stream() are not
semantically equiva
It's not required to specify Consumed:
- the specified Serdes from Produced are used for the consumer, too
- it would be invalid to specify a custom extractor (for correctness
reasons, we enforce the default timestamp extractor)
Note, that Streams API sets the metadata record timestamp on write,
`KStream#through()` currently lets you specify a `Produced`. Shouldn't it
also let you specify a `Consumed`. This would let you specify a time stamp
extractor.
