From dev-return-96008-archive-asf-public=cust-asf.ponee.io@kafka.apache.org Fri Jul 13 14:01:21 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id D8330180626 for ; Fri, 13 Jul 2018 14:01:20 +0200 (CEST) Received: (qmail 70165 invoked by uid 500); 13 Jul 2018 12:01:14 -0000 Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@kafka.apache.org Delivered-To: mailing list dev@kafka.apache.org Received: (qmail 70152 invoked by uid 99); 13 Jul 2018 12:01:14 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Jul 2018 12:01:14 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id A8847C00CD for ; Fri, 13 Jul 2018 12:01:13 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.879 X-Spam-Level: * X-Spam-Status: No, score=1.879 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=cloudera.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id z_7hHEC_av9t for ; Fri, 13 Jul 2018 12:01:11 +0000 (UTC) Received: from mail-ua0-f173.google.com (mail-ua0-f173.google.com [209.85.217.173]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 8EE935F3BA for ; Fri, 13 Jul 2018 12:01:11 +0000 (UTC) Received: by mail-ua0-f173.google.com with SMTP id y10-v6so636663uao.4 for ; Fri, 13 Jul 2018 05:01:11 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=XKlkLWYIpwegwQlD/krWv0xuhoRSRk04l7QXTMFEydQ=; b=g/yV32Zvu2fnCWJ3XEl5yCmBFp6urvN2M9wwhFg9PMTAo7fY3eTRAl/xIQ6LzpN46C AMYiAQ9f7A7EzMwHDUAEJ5vuX31E47xTVJlnQBd1G4DgeurQoxcRscaYAq8zWsMaGc97 SoLf+fZ7kpdSRdPQx0yMwscFjiroWhzcV9lyK/VpkxZjOi+9/baE5JRbw/nUxJoMAYV+ O4YSseDSgKogi4e1c2EmjICjz3YBjP23DGYl+ddG1KvkPe+EhaiYjJJDRY+HYArGWyhg tv7AXJT9GFDGpBAcIBwWyy/MKQVBimzIhRaxkxMGdc9e5SZStJOPxhxFoJD9ZrsMkzpA Fd4Q== X-Gm-Message-State: AOUpUlGQiooMV7rn2D5Ikk64ANbQhwLCt9MMVn3v3IH2ka3ziCnWGCYE Unm7KKFItHzyksq51Sn43OJwTocesb3mxKsdexFeTg== X-Google-Smtp-Source: AAOMgpetgZV5gPJTM1+7ZaUomBdPAISR6adOehVbUwR89osAraGWQTN9vv5pOxLK2h2QjA0P4FLWPH75b/0WAPOUPgk= X-Received: by 2002:a9f:3826:: with SMTP id p35-v6mr3993239uad.42.1531483265455; Fri, 13 Jul 2018 05:01:05 -0700 (PDT) MIME-Version: 1.0 References: <1531431315.515468.1439025968.1F6DDEDE@webmail.messagingengine.com> In-Reply-To: From: Andras Beni Date: Fri, 13 Jul 2018 14:00:54 +0200 Message-ID: Subject: Re: KIP-327: Add describe all topics API to AdminClient To: dev@kafka.apache.org Content-Type: multipart/alternative; boundary="000000000000047bd20570e03ccf" --000000000000047bd20570e03ccf Content-Type: text/plain; charset="UTF-8" The KIP looks good to me. However, if there is willingness in the community to work on metadata request with patterns, the feature proposed here and filtering by '*' or '.*' would be redundant. Andras On Fri, Jul 13, 2018 at 12:38 AM Jason Gustafson wrote: > Hey Manikumar, > > As Kafka begins to scale to larger and larger numbers of topics/partitions, > I'm a little concerned about the scalability of APIs such as this. The API > looks benign, but imagine you have have a few million partitions. We > already expose similar APIs in the producer and consumer, so probably not > much additional harm to expose it in the AdminClient, but it would be nice > to put a little thought into some longer term options. We should be giving > users an efficient way to select a smaller set of the topics they are > interested in. We have always discussed adding some filtering support to > the Metadata API. Perhaps now is a good time to reconsider this? We now > have a convention for wildcard ACLs, so perhaps we can do something > similar. Full regex support might be ideal given the consumer's > subscription API, but that is more challenging. What do you think? > > Thanks, > Jason > > On Thu, Jul 12, 2018 at 2:35 PM, Harsha wrote: > > > Very useful. LGTM. > > > > Thanks, > > Harsha > > > > On Thu, Jul 12, 2018, at 9:56 AM, Manikumar wrote: > > > Hi all, > > > > > > I have created a KIP to add describe all topics API to AdminClient . > > > > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP- > > 327%3A+Add+describe+all+topics+API+to+AdminClient > > > > > > Please take a look. > > > > > > Thanks, > > > --000000000000047bd20570e03ccf--