KIP call sounds good. Given that we only have an hour, it may make sense to prioritise the items that would benefit from KIP call discussion. I am leaving some comments below to hopefully help with prioritisation.
> - KIP-33: Add a time based log index This has been merged. > - KIP-50: Move Authorizer to o.a.k.common package Now that we have an ACL protocol request proposal, it has become apparent that the existing Authorizer interface could be better. Since we are introducing a new Java interface, it might make sense to take the chance to make these changes at the same time (Grant raised this point elsewhere as well). It would be good to discuss this. > - KIP-55: Secure Quotas for Authenticated Users There's a PR for this one (https://github.com/apache/kafka/pull/1753), so it seems like it just needs a reviewer. > - KIP-67: Queryable state for Kafka Streams This is mostly merged, additional testing and stabilisation is ongoing. > - KIP-70: Revise Partition Assignment Semantics on New Consumer's > Subscription There's a PR (https://github.com/apache/kafka/pull/1726) with an ongoing discussion. > Change > > and discuss some of the unvoted ones that are currently active and may need > more discussion? > - Time-based releases for Apache Kafka Good to discuss as Guozhang said. > - Java 7 support timeline Good to discuss as Guozhang said. Based on the feedback on the mailing list thread I started, I'm currently leaning towards proposing that we drop support for Java 7 on the next major release (which won't happen before next year from what I can tell). It would be good to reach agreement so that we can let users know ahead of time. > - KIP-4: ACL Admin Schema Good to discuss. > - KIP-73: Replication Quotas Good to discuss (even though there are enough binding +1 votes for the KIP to pass). > - KIP-74: Add FetchResponse size limit in bytes Vote passed. Given the above, my suggestion would be to discuss the following first (the items that are likely to affect the next release are above Java 7 support timeline, which could be discussed in a follow-up KIP meeting without much impact): 1. Time-based releases 2. KIP-4: ACL Admin Schema 3. KIP-50: Move Authorizer to o.a.k.common package 4. KIP-73: Replication Quotas 5. Java 7 support timeline If we have time, we can discuss other things, but it seems unlikely. Thoughts? Ismael On Fri, Aug 19, 2016 at 6:28 PM, Guozhang Wang <wangg...@gmail.com> wrote: > The list LGTM. And if the status check of the above five times was quick I > would suggest focus on the time-based release plan and Java 7 support > timeline especially. > > > Guozhang > > On Thu, Aug 18, 2016 at 11:22 AM, Jun Rao <j...@confluent.io> wrote: > > > Grant, > > > > That sounds like a good idea. I will send out an invite for this Tue at > > 11am. There are quite a few KIPs in your list and we probably can't cover > > them all in one call. Perhaps we can do a quick status check on those > that > > have been voted > > > > Thanks, > > > > Jun > > > > On Thu, Aug 18, 2016 at 10:55 AM, Grant Henke <ghe...@cloudera.com> > wrote: > > > > > I am thinking it might be a good time to have a Kafka KIP call. There > > are a > > > lot of KIPs and discussions in progress that could benefit from a > "quick" > > > call to discuss, coordinate, and prioritize. > > > > > > Some of the voted topics we could discuss are: > > > (I didn't include ones that were just voted or will pass just before > the > > > call) > > > > > > - KIP-33: Add a time based log index > > > - KIP-50: Move Authorizer to o.a.k.common package > > > - KIP-55: Secure Quotas for Authenticated Users > > > - KIP-67: Queryable state for Kafka Streams > > > - KIP-70: Revise Partition Assignment Semantics on New Consumer's > > > Subscription Change > > > > > > Some of the un-voted topics we could discuss are: > > > > > > - Time-based releases for Apache Kafka > > > - Java 7 support timeline > > > - KIP-4: ACL Admin Schema > > > - KIP-37 - Add Namespaces to Kafka > > > - KIP-48: Delegation token support for Kafka > > > - KIP-54: Sticky Partition Assignment Strategy > > > - KIP-63: Unify store and downstream caching in streams > > > - KIP-66: Add Kafka Connect Transformers to allow transformations to > > > messages > > > - KIP-72 Allow Sizing Incoming Request Queue in Bytes > > > - KIP-73: Replication Quotas > > > - KIP-74: Add FetchResponse size limit in bytes > > > > > > As a side note it may be worth moving some open KIPs to a "parked" list > > if > > > they are not being actively worked on. We can include a reason why as > > well. > > > Reasons could include being blocked, parked, dormant (no activity), or > > > abandoned (creator isn,t working on it and others can pick it up). We > > would > > > need to ask the KIP creator or define some length of time before we > call > > a > > > KIP abandoned and available for pickup. > > > > > > Some KIPs which may be candidates to be "parked" in a first pass are: > > > > > > - KIP-6 - New reassignment partition logic for rebalancing (dormant) > > > - KIP-14 - Tools standardization (dormant) > > > - KIP-17 - Add HighwaterMarkOffset to OffsetFetchResponse (dormant) > > > - KIP-18 - JBOD Support (dormant) > > > - KIP-23 - Add JSON/CSV output and looping options to > > > ConsumerGroupCommand (dormant) > > > - KIP-27 - Conditional Publish (dormant) > > > - KIP-30 - Allow for brokers to have plug-able consensus and meta > data > > > storage sub systems (dormant) > > > - KIP-39: Pinning controller to broker (dormant) > > > - KIP-44 - Allow Kafka to have a customized security protocol > > (dormant) > > > - KIP-46 - Self Healing (dormant) > > > - KIP-47 - Add timestamp-based log deletion policy (blocked - by > > KIP-33) > > > - KIP-53 - Add custom policies for reconnect attempts to > > NetworkdClient > > > - KIP-58 - Make Log Compaction Point Configurable (blocked - by > > KIP-33) > > > - KIP-61: Add a log retention parameter for maximum disk space usage > > > percentage (dormant) > > > - KIP-68 Add a consumed log retention before log retention (dormant) > > > > > > Thank you, > > > Grant > > > -- > > > Grant Henke > > > Software Engineer | Cloudera > > > gr...@cloudera.com | twitter.com/gchenke | linkedin.com/in/granthenke > > > > > > > > > -- > -- Guozhang >
