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 C373B200C28 for ; Mon, 27 Feb 2017 01:00:53 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id C1F59160B77; Mon, 27 Feb 2017 00:00:53 +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 15868160B6E for ; Mon, 27 Feb 2017 01:00:52 +0100 (CET) Received: (qmail 61403 invoked by uid 500); 27 Feb 2017 00:00:52 -0000 Mailing-List: contact issues-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list issues@camel.apache.org Received: (qmail 61394 invoked by uid 99); 27 Feb 2017 00:00:52 -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; Mon, 27 Feb 2017 00:00:52 +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 CECD3C0B7C for ; Mon, 27 Feb 2017 00:00:51 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -2.347 X-Spam-Level: X-Spam-Status: No, score=-2.347 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-2.999, SPF_NEUTRAL=0.652] autolearn=disabled 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 zW5wlxL913_P for ; Mon, 27 Feb 2017 00:00:51 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id E31DF60E17 for ; Mon, 27 Feb 2017 00:00:50 +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 7466FE0630 for ; Mon, 27 Feb 2017 00:00:49 +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 D84222413C for ; Mon, 27 Feb 2017 00:00:48 +0000 (UTC) Date: Mon, 27 Feb 2017 00:00:48 +0000 (UTC) From: "Sverker Abrahamsson (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CAMEL-10901) Add support to Kafka consumer to seek to end of topic MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 27 Feb 2017 00:00:53 -0000 Sverker Abrahamsson created CAMEL-10901: ------------------------------------------- Summary: Add support to Kafka consumer to seek to end of topic Key: CAMEL-10901 URL: https://issues.apache.org/jira/browse/CAMEL-10901 Project: Camel Issue Type: New Feature Components: camel-kafka Affects Versions: 2.19.0 Reporter: Sverker Abrahamsson Priority: Minor Kafka 2.19.0-SNAPSHOT adds seekToBeginning parameter to read all events of a topic from beginning. In my application I'm not interested of what has happened before it is started, so I need the opposite so that seekToEnd is called on the consumer. The pull request for this feature request will change the parameter to seekTo which can be set to either beginning or end, which is analog with how other parameters on this consumer is set. -- This message was sent by Atlassian JIRA (v6.3.15#6346)