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 37056200D0E for ; Tue, 26 Sep 2017 12:13:50 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 355061609C1; Tue, 26 Sep 2017 10:13:50 +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 7B4EB1609B4 for ; Tue, 26 Sep 2017 12:13:49 +0200 (CEST) Received: (qmail 98166 invoked by uid 500); 26 Sep 2017 10:13:48 -0000 Mailing-List: contact user-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list user@flink.apache.org Received: (qmail 98152 invoked by uid 99); 26 Sep 2017 10:13:48 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Sep 2017 10:13:48 +0000 Received: from Tzu-Lis-MBP.fritz.box.mail (dslb-094-222-124-158.094.222.pools.vodafone-ip.de [94.222.124.158]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 9C3EE1A0040; Tue, 26 Sep 2017 10:13:45 +0000 (UTC) Date: Tue, 26 Sep 2017 12:13:44 +0200 From: "Tzu-Li (Gordon) Tai" To: Jagadish Gangulli , user@flink.apache.org Cc: Till Rohrmann Message-ID: In-Reply-To: References: Subject: Re: Regarding flink-cassandra-connectors X-Mailer: Airmail (442) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="59ca2858_687c4373_118" archived-at: Tue, 26 Sep 2017 10:13:50 -0000 --59ca2858_687c4373_118 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Ah, sorry I just realized Till also answered your question on your cross-= post at dev=40. It=E2=80=99s usually fine to post questions to just a single mailing list= :) On 26 September 2017 at 12:10:55 PM, Tzu-Li (Gordon) Tai (tzulitai=40apac= he.org) wrote: Hi Jagadish, Yes, you are right that the =46link Cassandra connector uses the Datastax= drivers internally, which is also the case for all the other =46link con= nectors; e.g., the Kafka connector uses the Kafka Java client, Elasticear= ch connector uses the ES Java client, etc. The main advantage when using these =46link first-class supported connect= ors is basically the following: - Most importantly, the connectors work with =46link=E2=80=99s checkpoint= ing mechanism to achieve exactly-once or at-least-once guarantees. You ca= n read more about that here =5B1=5D. - The connectors are built on =46link=E2=80=99s abstractions of streaming= sources / sinks. What this means is you can basically swap out / plug-in= / add sources or sinks to various external systems without altering the = main business logic in your processing pipeline. i.e., also sinking your = data to Elasticsearch would be as simple as also adding a Elasticsearch s= ink to your pipeline output alongside your Cassandra sink. Hope this clarifies some points for you=21 Cheers, Gordon =5B1=5D=C2=A0https://ci.apache.org/projects/flink/flink-docs-release-1.3/= internals/stream=5Fcheckpointing.html On 26 September 2017 at 11:03:16 AM, Jagadish Gangulli (jagadishg=40gmail= .com) wrote: Hi, I have been recently into the application development with flink. We are = trying to use the flink-apache connectors to get the data in and out from= Cassandra. We attempted both Datastax drivers and =46link-cassandra connectors.=C2=A0= In this process felt that flink-cassandra connector is more of a wrapper= on top of data stax cassandra drivers. Hence could some one please explain the benefits of the flink-cassandra-c= onnectors over the data stax driver apis. We are looking for the APIs whi= ch are better in terms of performance. Please let me know your thoughts. Thanks & Regards, Jagadisha G --59ca2858_687c4373_118 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline