Changing number of partitions is complicated in some use-cases and easy in other cases (when you use Kafka as a big pipe of events on the way to another system). I like making easy things easy and complex things complicated. Having defaults for both will allow the easy cases to be even easier.
In my experience lack of default doesn't force people to think - it gets them to pick a random number... (not sure there is any configuration that can get anyone to think, unfortunately). On Tue, Apr 30, 2019 at 10:22 AM Almog Gavra <al...@confluent.io> wrote: > I have a preference toward requiring specifying partitions per topic, but > I'm happy to be convinced otherwise. Changing replication factor after the > fact is easy, but changing partitions is complicated since historical state > gets messed up, so it could be beneficial to force clients to think about > it up front. Furthermore, I see partitioning as a function on the scale of > the data while replication is a function of cluster capacity. Thoughts? > > On Tue, Apr 30, 2019 at 8:58 AM Ismael Juma <isma...@gmail.com> wrote: > > > Thanks for the KIP, Almog. This is a good change. I think we should also > > allow the partition count broker default to be used (the one used for > auto > > topic creation). > > > > Ismael > > > > On Tue, Apr 30, 2019, 8:39 AM Almog Gavra <al...@confluent.io> wrote: > > > > > Hello Everyone, > > > > > > I'd like to start a discussion on KIP-464: > > > > > > > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-464%3A+Default+Replication+Factor+for+AdminClient%23createTopic > > > > > > It's about allowing users of the AdminClient to supply only a partition > > > count and to use the default replication factor configured by the kafka > > > cluster. Happy to receive any and all feedback! > > > > > > Cheers, > > > Almog > > > > > > -- *Gwen Shapira* Product Manager | Confluent 650.450.2760 | @gwenshap Follow us: Twitter <https://twitter.com/ConfluentInc> | blog <http://www.confluent.io/blog>
