Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 05623200C7B for ; Sat, 20 May 2017 20:30:10 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 03DE9160BBE; Sat, 20 May 2017 18:30:10 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 46633160BA7 for ; Sat, 20 May 2017 20:30:09 +0200 (CEST) Received: (qmail 64851 invoked by uid 500); 20 May 2017 18:30:08 -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 64840 invoked by uid 99); 20 May 2017 18:30:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 20 May 2017 18:30:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id CFCB11A02EE for ; Sat, 20 May 2017 18:30:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id rEYpKUbUflDA for ; Sat, 20 May 2017 18:30:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 4517860CD9 for ; Sat, 20 May 2017 18:30:05 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 73E3DE06BF for ; Sat, 20 May 2017 18:30:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1AE7921B57 for ; Sat, 20 May 2017 18:30:04 +0000 (UTC) Date: Sat, 20 May 2017 18:30:04 +0000 (UTC) From: "Jorge Quilcate (JIRA)" To: dev@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (KAFKA-5266) Follow-up improvements for consumer offset reset tool (KIP-122) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sat, 20 May 2017 18:30:10 -0000 [ https://issues.apache.org/jira/browse/KAFKA-5266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16018581#comment-16018581 ] Jorge Quilcate commented on KAFKA-5266: --------------------------------------- I like 'to-current', I'll implement it. On 4, you're right, NPE is possible in those cases. Wouldn't be better to filter those 'null's and print some warning logs before #toMap? And then catch any other exception on the all #resetOffsets implementation? > Follow-up improvements for consumer offset reset tool (KIP-122) > --------------------------------------------------------------- > > Key: KAFKA-5266 > URL: https://issues.apache.org/jira/browse/KAFKA-5266 > Project: Kafka > Issue Type: Bug > Components: tools > Reporter: Jason Gustafson > Assignee: Jorge Quilcate > Fix For: 0.11.0.0 > > > 1. We should try to ensure that offsets are in range for the topic partition. We currently only verify this for the shift option. > 2. If you provide a CSV file, you shouldn't need to specify one of the --all-topics or --topic options. > 3. We currently support a "reset to current offsets" option if none of the supported reset options are provided. This seems kind of useless. Perhaps we should just enforce that one of the reset options is provided. > 4. The command fails with an NPE if we cannot find one of the offsets we are trying to reset. It would be better to raise an exception with a friendlier message. -- This message was sent by Atlassian JIRA (v6.3.15#6346)