Page History

...

Compatibility, Deprecation, and Migration Plan

 This is a breaking, incompatible change because

...

TimestampExtractor

...

 interface gets changed

...

. However, it only affect uses that provide a custom timestamp extractor. By default no code change is required and the overall behavior is the same as before this KIP (using default timestamp extractor user gets an exception in case of a negative timestamp).

• Even if the exception is throw from a different point and the exception message changes (the exception type is the same: StreamsException) the use cannot recover from the exception anyway (i.e., user cannot recover with current behavior and this will not change)

Required Code code changes:

• Custom timestamp extractors must be updated:
  • recompile to avoid runtime exception
  • code change to adapt to new interface (to make it compile)

...