[jira] [Resolved] (KAFKA-8452) Possible Suppress buffer optimization: de-duplicate prior value

["John Roesler (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KAFKA-8452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Roesler resolved KAFKA-8452.
---------------------------------
    Resolution: Fixed

> Possible Suppress buffer optimization: de-duplicate prior value
> ---------------------------------------------------------------
>
>                 Key: KAFKA-8452
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8452
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>            Reporter: John Roesler
>            Assignee: John Roesler
>            Priority: Major
>
> As of KAFKA-8199, the suppression buffers have to track the "prior value" in addition to the "old" and "new" values for each record, to support transparent downstream views.
> In many cases, the prior value is actually the same as the old value, and we could avoid storing it separately. The challenge is that the old and new values are already serialized into a common array (as a Change via the FullChangeSerde), so the "prior" value would actually be a slice on the underlying array. But, of course, Java does not have array slices.
> To get around this, we either need to switch to ByteBuffers (which support slices) or break apart the serialized Change into just serialized old and new values.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)