mjsax commented on code in PR #21414: URL: https://github.com/apache/kafka/pull/21414#discussion_r2785857071
########## docs/streams/developer-guide/processor-api.md: ########## @@ -309,7 +309,7 @@ You can create a persistent, versioned state store by passing a [VersionedBytesS Each versioned store has an associated, fixed-duration _history retention_ parameter which specifies long old record versions should be kept for. In particular, a versioned store guarantees to return accurate results for timestamped retrieval operations where the timestamp being queried is within history retention of the current observed stream time. -History retention also doubles as its _grace period_ , which determines how far back in time out-of-order writes to the store will be accepted. A versioned store will not accept writes (inserts, updates, or deletions) if the timestamp associated with the write is older than the current observed stream time by more than the grace period. Stream time in this context is tracked per-partition, rather than per-key, which means it's important that grace period (i.e., history retention) be set high enough to accommodate a record with one key arriving out-of-order relative to a record for another key. +History retention also doubles as its _grace period_ , which determines how far back in time out-of-order writes to the store will be accepted. A versioned store will not accept writes (inserts, updates, or deletions) if the timestamp associated with the write is older than the current observed stream time by more than the grace period. Stream time in this context refers to task-level stream time (tracked per-partition, rather than per-key), which is preserved across restarts, unlike operator-level stream time used by DSL window operators. It's important that grace period be set high enough to accommodate a record with one key arriving out-of-order relative to a record for another key. Review Comment: For versioned kv-stores, it's also operator level stream-time, not task-level. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
