They are defined at the broker level as a default for all topics that do not have an override for those configs. Both (and many other configs) can be overridden for individual topics using the command line tools.
-Todd On Wed, Mar 8, 2017 at 12:36 PM, Nicolas Motte <lingusi...@gmail.com> wrote: > Hi everyone, I have another question. > Is there any reason why retention and cleanup policy are defined at cluster > level and not topic level? > I can t see why it would not be possible from a technical point of view... > > 2017-03-06 14:38 GMT+01:00 Nicolas Motte <lingusi...@gmail.com>: > > > Hi everyone, > > > > I understand one of the reasons why Kafka is performant is by using > > zero-copy. > > > > I often hear that when encryption is enabled, then Kafka has to copy the > > data in user space to decode the message, so it has a big impact on > > performance. > > > > If it is true, I don t get why the message has to be decoded by Kafka. I > > would assume that whether the message is encrypted or not, Kafka simply > > receives it, appends it to the file, and when a consumer wants to read > it, > > it simply reads at the right offset... > > > > Also I m wondering if it s the case if we don t use keys (pure queuing > > system with key=null). > > > > Cheers > > Nico > > > > > -- *Todd Palino* Staff Site Reliability Engineer Data Infrastructure Streaming linkedin.com/in/toddpalino
