[
https://issues.apache.org/jira/browse/KAFKA-8318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17211842#comment-17211842
]
Ilia Pasynkov commented on KAFKA-8318:
--------------------------------------
Hello, [~vvcephei]
I really need some advice where that session merging logic takes place so that
I could correct its behaviour. I've checked lots of links from
SuppressScenarioTest method (mentioned in
[https://github.com/apache/kafka/pull/6654#discussion_r280231439]) and I would
appreciate very much your advice regarding session merging logic location
> Session Window Aggregations generate an extra tombstone
> -------------------------------------------------------
>
> Key: KAFKA-8318
> URL: https://issues.apache.org/jira/browse/KAFKA-8318
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: John Roesler
> Assignee: Ilia Pasynkov
> Priority: Minor
> Labels: newbie++
>
> See the discussion
> https://github.com/apache/kafka/pull/6654#discussion_r280231439
> The session merging logic generates a tombstone in addition to an update when
> the session window already exists. It's not a correctness issue, just a small
> performance hit, because that tombstone is immediately invalidated by the
> update.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
