Thank you very much for taking the time to read it.

bq. In the 'Proposed Changes' section, can you expand 'OCC' ?
I've made the 'OCC' into a link pointing to the appropriate Wiki page 
explaining what it is. This is not a particularly important part of the change, 
it is just to reference the similarity between this proposal and the version 
control offered by OCC.

bq. Is it possible to enumerate the keys ?
Do you mean hard-coding the header key used, rather than using a free-text 
solution? If I were to hard-code header with key "version", for example, then 
this may conflict with other clients that already use this header for something 
else, making it cumbersome for them to try and use this strategy, should they 
want it.
If I misunderstood your points, then please correct me. I appreciate the 
feedback!    On Thursday, April 5, 2018, 5:13:47 PM GMT+2, Ted Yu 
<> wrote:  
 In the 'Proposed Changes' section, can you expand 'OCC' ?

bq. Specifically changing this to anything other than "*offset*"

Is it possible to enumerate the keys ? In the future, more metadata would
be defined in record header - it is better to avoid collision.


On Thu, Apr 5, 2018 at 2:05 AM, Luís Cabral <>

> This is embarassingly hard to fix... going again...
> ----
> KIP-280:
> KAFKA/KIP-280%3A+Enhanced+log+compaction
> -----
> Pull-4822:
>    On Thursday, April 5, 2018, 11:03:22 AM GMT+2, Luís Cabral
> <> wrote:
>  Fixing the links:KIP-280:
> KAFKA/KIP-280%3A+Enhanced+log+compactionPull-4822:  https://
> On 2018/04/0508:44:00, Luís Cabral <> wrote:
> > Helloall,>
> > Starting adiscussion for this feature.>
> >KIP-280  :
> 280%3A+Enhanced+log+compactionPull-4822:
> kafka/pull/4822>
> > KindRegards,Luís>

Reply via email to