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 BC39E200B17 for ; Tue, 7 Jun 2016 00:23:31 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id BAC95160A55; Mon, 6 Jun 2016 22:23:31 +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 DB4B7160A24 for ; Tue, 7 Jun 2016 00:23:30 +0200 (CEST) Received: (qmail 94662 invoked by uid 500); 6 Jun 2016 22:23:30 -0000 Mailing-List: contact users-help@apex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@apex.apache.org Delivered-To: mailing list users@apex.apache.org Received: (qmail 94640 invoked by uid 99); 6 Jun 2016 22:23:29 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Jun 2016 22:23:29 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 61A04C137C for ; Mon, 6 Jun 2016 22:23:29 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.179 X-Spam-Level: * X-Spam-Status: No, score=1.179 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_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id qzatW8URkU_z for ; Mon, 6 Jun 2016 22:23:27 +0000 (UTC) Received: from mail-qk0-f174.google.com (mail-qk0-f174.google.com [209.85.220.174]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id F3CAE5FB40 for ; Mon, 6 Jun 2016 22:23:26 +0000 (UTC) Received: by mail-qk0-f174.google.com with SMTP id u63so14850337qkh.0 for ; Mon, 06 Jun 2016 15:23:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=SHt7fOj3/poF0NaS4E3rvBgIkJ/WIb4APEAUne0X0qI=; b=VqmlF+ZGeUot3Flj3tKg1Q0N6nEh9Ln5A25CEonzXT8ejty3iGLAzYQhAnSjl0jPyn kEcV/mnAPamriMniyqyBT6R+YNoNYyDSu9R3LJzX6hE14m2kLqeG0ox+Lunw7+uF1JA6 rOEJkD7VHobp+0nF1tUTT5m3Eq8BHOgwc14+v921PnvPP6zgd0SkWiRYHeZ9dT9E4khK RKqkfNTq3OLnBAK3OY0eLF5ULkFXz8s3VISQbgYrEvMZlP+b1iGUW8NqJS1Qyv8zJgFm js7m7XwtQP8MEXVJPL+A5GtY8buLN9qEOppdL6WLV/Y7UV3bHRU+RZ/GgKzmy36aE7sY RPeQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=SHt7fOj3/poF0NaS4E3rvBgIkJ/WIb4APEAUne0X0qI=; b=AcXRdd6F/JyOnZofd+hqQef2hgAJ8nxaX4SsZmFvVWA/a32Nh0Eo/eBSMVgyUoLybD +BI8AgytVi70Av9j//RjF3F3CIobfTi1Wh7P0nf1xl2CVBwpZ9fjnPDNyma4Z431us+q dnQjJqqf7cRZS9+1mL/0JXosNAKkzLbqqViW3be3/YTmIiENBH1VTXPdFfP0i1n9TFO2 GKswncHsqeGRtrfv9exzZglmB2ykYFQj6tj8CJHPNEtkih7muwz2vc549nTm78fVlsQo mPcRpiC7tBHdJO8fRvy2hoajW+l/fbXz2jijOkBZB3+GkpVJhtNAnurs3ctSp8iARfDu NTlA== X-Gm-Message-State: ALyK8tIQtznIy92PQQoEVXgYlWtcIAT8ZDsrGURgcJ2suXmZDX7lLyY52fd52X8hjOdnPeJbtH4wRaNKArjvDQ== X-Received: by 10.55.207.149 with SMTP id v21mr18580244qkl.195.1465251806127; Mon, 06 Jun 2016 15:23:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.55.71.144 with HTTP; Mon, 6 Jun 2016 15:23:25 -0700 (PDT) In-Reply-To: <0614D484-1FA4-46B8-8567-29B36D4A4EF6@target.com> References: <0614D484-1FA4-46B8-8567-29B36D4A4EF6@target.com> From: Thomas Weise Date: Mon, 6 Jun 2016 15:23:25 -0700 Message-ID: Subject: Re: kafka offset commit To: users@apex.apache.org Content-Type: multipart/alternative; boundary=001a114592ac692ed50534a3852b archived-at: Mon, 06 Jun 2016 22:23:31 -0000 --001a114592ac692ed50534a3852b Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Raja, Which Kafka version are you using? With the new 0.9 connector there is no need for the offset manager: https://github.com/apache/apex-malhar/tree/master/kafka/src/main/java/org/a= pache/apex/malhar/kafka Thanks, Thomas On Mon, Jun 6, 2016 at 3:06 PM, Raja.Aravapalli wrote: > Hi > > Can someone please help me understand, where will the offsets be stored > when consuming with =E2=80=9C*KafkaSinglePortStringInputOperator*=E2=80= =9D ? > > And, how to handle restarts ? > > > I worked with Storm earlier, Storm maintains the offsets in zookeeper and > client id is maintained for every consumer, using which > > - we can see what is the current offset status for a given partition & > modify them as well using zookeeper-cli !! > - restarts can be handled > > > As per the Apex documentation, I can see, that using OffsetManager we can > handle the restarts effectively, but couldn=E2=80=99t find any examples t= o refer=E2=80=A6 > > How clientId can be used to retrieve offsets status > And ability to edit the offsets etc > > can someone pls help me find this ? > > > Thanks a lot!! > > > -Regards, > Raja. > > > > --001a114592ac692ed50534a3852b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Raja,

Which Kafka version are you us= ing?

With the new 0.9 connector there is no need f= or the offset manager:


Thanks,
Thomas


On Mon, Jun 6, 2016 at 3:06 PM, Raja.Aravapalli <Raja.Aravapalli@target.com> wrote:
Hi=C2=A0

Can someone please help me understand, where will the offsets be store= d when consuming with =E2=80=9CKafkaSinglePortStringInputOperator=E2= =80=9D =C2=A0?

And, how to handle restarts ?


I worked with Storm earlier, Storm maintains the offsets in zookeeper = and client id is maintained for every consumer, using which=C2=A0

- we can see what is the current offset status for a given partition &= amp; modify them as well using zookeeper-cli !!
- restarts can be handled


As per the Apex documentation, I can see, that using OffsetManager we = can handle the restarts effectively, but couldn=E2=80=99t find any examples= to refer=E2=80=A6=C2=A0

How clientId can be used to retrieve offsets status
And ability to edit the offsets etc

can someone pls help me find this ?=C2=A0


Thanks a lot!!


-Regards,
Raja.




--001a114592ac692ed50534a3852b--