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 - 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
and discuss some of the unvoted ones that are currently active and may need more discussion? - Time-based releases for Apache Kafka - Java 7 support timeline - KIP-4: ACL Admin Schema - KIP-73: Replication Quotas - KIP-74: Add FetchResponse size limit in bytes 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 >
