Major Description
Right now Streams API unversally represents time as ms-since-unix-epoch.
There's nothing wrong, per se, with this, but Duration is more ergonomic for an API.
What we don't want is to present a heterogeneous API, so we need to make sure the whole Streams API is in terms of Duration.
Implementation note: Durations potentially worsen memory pressure and gc performance, so internally, we will still use longMs as the representation.
Attachments
Issue Links
- is a parent of
-
KAFKA-7477 Improve Streams close timeout semantics
-
- Resolved
-
- links to
(1 links to, 2 mentioned in)